Construction Cloud Project Management in Houston: The IT Checklist Before You Move

I’m a Lead vCIO at Uprite, so I spend a lot of time on the IT side of Procore rollouts, and the vendor’s implementation team is usually good at its own part of the work. It’ll build your project templates, load your cost codes and train your project managers. It won’t touch your Microsoft 365 tenant, your trailer firewall, your iPads or the Sage server in the back room. Not its job.

So the IT side gets done by whoever’s closest. Often the controller. Sometimes nobody. The platform goes live, and a few weeks later a superintendent can’t load drawings on trailer Wi-Fi, a sub who left in March can still read the RFI log, and nobody can say whose login the ERP sync runs under.

This checklist is for that side of the move. It’s written for Houston general contractors and specialty trades moving project management into Procore, into Autodesk Forma (the platform Autodesk called Autodesk Construction Cloud until its 2026 rename), or into something similar. It assumes you’ve already decided what moves. If you haven’t, start with which construction workloads belong in the cloud.

What does moving to cloud project management change for a contractor’s IT?

Cloud project management means a contractor runs RFIs, submittals, drawings, daily logs and change orders in a hosted platform instead of on a file server and in email. The vendor runs the servers, the software and its own security. The contractor still owns every account, every device, every network the field connects from, and its own copy of the records.

That split surprises people. You bought software, so the software company handles the software, right? It does. It just doesn’t handle anything on your side of the sign-in screen.

The right-hand column is the checklist.

Why is the IT side harder for Houston contractors?

Growth, mostly. And weather.

We pulled the 2025 annual averages from the Bureau of Labor Statistics Quarterly Census of Employment and Wages for private construction in Harris, Fort Bend and Montgomery counties. Together they had 10,889 construction establishments employing 216,626 people, which is 18,724 more workers than a year earlier and a 9.5% jump in a single year for the 3 counties combined.

The number of firms went up by 5. Just 5.

Houston contractors didn’t multiply in 2025. They got bigger. The average establishment across the 3 counties went from 18.2 people to 19.9, and a Harris County construction establishment now averages about 22, against 8.7 nationally in the same data. Big enough for real IT. Too small to hire one. Every new hire becomes another login, another tablet and another name in the project directory, managed by the same small office that was already stretched thin before anyone new showed up on the payroll.

And hiring hasn’t slowed. The Associated General Contractors of America reported in September 2026 that Houston-Pasadena-The Woodlands added the most construction jobs of any metro, 13,100 or 5%, between July 2025 and July 2026.

Then there’s the weather. After Hurricane Beryl hit on July 8, 2024, CenterPoint faced 2.26 million outages, and 88,000 of its customers were still without power a full 8 days later, according to the Texas Tribune’s running storm coverage. A cloud platform doesn’t go down in a hurricane. Your trailer’s connection to it does.

Heat counts too. Apple says iPhones and iPads are designed for ambient temperatures between 32 and 95 degrees Fahrenheit, and the National Weather Service puts the normal August high at Bush Intercontinental, based on its 1991 to 2020 climate normals, at 94.9. That’s an average afternoon, in the shade, before anyone leaves a tablet on a dashboard. Budget for replacements.

Procore and Autodesk Forma IT requirements, side by side

Both vendors publish more than most buyers read. The table sums up their own documentation, checked in September 2026.

Procore’s figures come from its support site, and Autodesk’s come from its help pages on installing the mobile app and on the Data Connector. Procore also asks for at least 64 GB of free storage on each mobile device, with 5 to 10 GB per project. That rules out old iPads.

What’s on the IT checklist for moving project management to the cloud?

10 items. They’re in the order I’d tackle them, and the first 3 should be done before anyone outside the office gets an invitation. I’ll use Procore for the specifics because it publishes the most detail, but every item applies to Autodesk Forma too.

1. Put sign-in behind your own identity provider

Procore supports single sign-on through Microsoft Entra ID, Okta, OneLogin and Google, and any other SAML 2.0 provider through a custom setup. It works by email domain. You tell Procore which of your domains to target, Procore Support switches on federated sign-in for them, and from then on anyone with an address on those domains signs in through your identity provider.

Do it before rollout. Your people get the same Microsoft account, the same multifactor prompt and the same Conditional Access rules you already use for email. For anyone on a targeted domain, Procore says multifactor has to be set up in your identity provider, which is where you want it anyway. When someone leaves, disabling one account in Microsoft 365 blocks their sign-in to the project platform too.

One catch. Procore’s own documentation says it doesn’t support automatic provisioning with single sign-on, so every user still has to exist in the Directory tool. Disabling someone in Entra ID stops the sign-in. It doesn’t remove the directory record. Somebody still has to.

Keep one break-glass administrator outside single sign-on. Just one. Give it a long random password in a vault the owner controls, and don’t let it belong to whoever happened to sign the contract. If the only company admin is a project executive who later quits, you’ll be asking the vendor’s support team to hand your own records back.

2. Decide who can invite outsiders, and who removes them

Seats aren’t the limit here. Procore prices by annual construction volume, and its pricing page says it’ll never charge you for adding more users. Unlimited seats are great for budgets. Access control, less so.

Every project pulls in subcontractors, the owner’s rep, the architect, a testing lab and sometimes a lender. None of them will ever sign in through your identity provider, because they don’t work for you, and Procore’s directory adds a detail that makes that worse than it first sounds. A user created in a project’s Directory tool is automatically added to the company directory, and Procore notes they can log in even if no invitation was sent. Add a sub’s estimator to one job and they’re in your company directory until someone takes them out.

My honest take? Single sign-on protects the people you already manage well. The exposure is everyone else. So write down 2 rules. Who’s allowed to add someone from outside the company, and with which permission template? And who removes them? My answer is at project closeout, every time, with a quarterly directory review on long jobs. Employees leave through HR. Former subs leave through nobody.

For the outside accounts, turn on Procore’s own company-wide multifactor requirement. It uses an authenticator app or a text message, and you set an enforcement deadline so people get warning before it bites.

3. Enroll field tablets and phones before the app goes on them

Mobile is where field records get made now. When AGC and Sage polled more than 1,100 contractors for their 2025 outlook, 69% reported using mobile software for daily field reports. Those reports live on devices. Manage the devices.

Enroll every company tablet and phone in a mobile device management tool like Microsoft Intune before you hand it out. Push the app from there, set an operating system floor that matches the vendor’s minimum, and block devices that fall under it. An iPad stuck on an older version won’t run the current Procore app, which requires iOS 17.1 or later. Shared trailer tablets need their own profile, because 4 people working under 1 person’s login wrecks the audit trail that makes a daily log worth anything when a delay claim or a pay dispute lands.

Lost devices matter too. A tablet left on a tailgate in Katy holds downloaded drawings and jobsite photos. A managed one can be wiped remotely in a minute. An unmanaged one can’t.

4. Open the right paths on the office and trailer firewalls

Start with the vendor’s own list. Procore publishes the domains to allow on your network. Its simplest recommendation is a wildcard entry for *.procore.com with outbound HTTPS and secure WebSocket traffic on port 443. The detailed list also includes third-party services the app depends on, such as Amazon S3 storage, and Procore asks IT teams to bookmark the page and check it regularly for changes. Procore revised it on September 15, 2026. So yes, it changes.

Office firewalls usually cope. Trailer firewalls and cellular routers are different, because somebody set them up in a hurry with a web filter that’s never heard of those third-party domains or the storage services behind them. The symptom is a drawing set that loads over a phone’s own data plan but not over trailer Wi-Fi. Test every site against the vendor’s list before the first superintendent calls it in, and if your firewalls decrypt and inspect traffic, exclude the platform’s domains from inspection.

5. Plan for the day the trailer goes dark

Offline mode is narrower than people assume. Procore’s mobile app only shows items that were cached or recently viewed while online, and anything you do offline waits until a connection comes back. Delete the app and the cache goes with it. Drawings have to be downloaded one discipline at a time, and downloaded sets don’t update themselves. They need a re-sync on a working connection to pick up the latest revision.

So make downloading a habit. Before a storm, a carrier cutover or a move to a new site, have superintendents pull the current set onto every device they’ll use. Add a second carrier or cellular failover at any trailer running more than a handful of people. We covered what a dead uplink does to a schedule in the IT risks that stop projects on Texas job sites.

Hurricane season opens June 1. Run the drill in May.

6. Make sure project email actually arrives

Email still matters here. Procore sends notifications from its own domains, including procore.com and procoretech.com, over dedicated IP addresses, and its support team tells customers to add those addresses to an email allow list. RFI and correspondence replies also flow back into the platform through email.

Filters like Microsoft Defender for Office 365 can quarantine automated mail from outside senders, especially when it arrives in bursts carrying links. Add the vendor’s sending domains and addresses to your allow rules, watch the quarantine report for the first month, and tell project managers where to look. An RFI answer stuck in quarantine for 9 days is a schedule problem dressed up as an IT one.

Check the inbound side too. Each Procore project’s Emails tool has its own address, and the default setting lets anyone send email into it. Restrict it to your company or project directory unless you’ve got a reason not to.

7. Move active jobs, and archive closed ones

Don’t migrate 15 years of job folders into a new platform. Nobody needs that. Move active projects, plus anything still inside a warranty period, and archive the rest in storage you control.

Clean the structure on the way in. Procore’s tools, like Drawings, Submittals and RFIs, replace a lot of the old folder tree, and its Documents tool handles large files well, with a 50 GB limit on a single file upload. Procore Drive, the desktop sync app, only runs on Windows 10 or newer, not on Macs, and a per-machine install needs local administrator rights. Check that before the estimating team’s MacBooks become a surprise.

Findability is the point. Procore’s own 2025 Future State of Construction research, drawn from more than 1,200 construction decision-makers, found that 18% of project time is lost searching for data. Dumping the old file server into a new platform just moves that search somewhere more expensive. If closed jobs are headed to SharePoint instead, our post on what moves, what stays and what breaks covers the path and sync limits that catch contractors.

8. Give every integration its own account

Integrations quietly break when they run under a person. Procore says it plainly. An app that uses a person’s authorization can see and act on the same items that person can, and no more. When that person leaves and their account gets disabled, the app loses its access with them. Job costs stop syncing. Nobody gets an error. The numbers just stop moving.

Procore’s answer is the Developer Managed Service Account, which gets its own directory user and its own permissions. The older service accounts it replaced were deprecated in December 2021 and sunset on March 18, 2025, and Procore says integrations that weren’t migrated stopped working. Use service accounts wherever the connector allows it, record who owns each one, and put them on your offboarding list. For Sage 300 CRE shops, the Procore connector also runs as a Windows service on your own Sage server, which we cover in why construction ERP systems need a managed IT partner.

9. Export every project before you mark it inactive

This one gets skipped more than any other. It shouldn’t.

Texas gives claims against a contractor a long tail. Section 16.009 of the Civil Practice and Remedies Code allows suits against someone who builds or repairs an improvement to real property up to 10 years after substantial completion, and a written claim presented inside that window extends it by 2 more years. Architects and engineers carry the same 10-year period under Section 16.008. Your subscription may not last that long, and even if it does, you’ll want your own copy the day a claim letter shows up.

Procore adds a wrinkle. Its Extracts desktop app downloads a project’s records, mostly as PDFs, with documents and photos in their original formats. But only projects set to Active can be extracted. Mark a job inactive first and Extracts can’t reach it. Leaving has a clock too. Procore’s published standard subscription agreement, in the 2022 revision we read, gives a former customer 30 days of read-only access to its data after termination, and after that Procore has no obligation to keep it. Your own order form may differ. Read it.

So set a closeout rule. Export the full record while the project is still active, store it in company-owned storage, and back that storage up separately with data backup services you’ve actually restored from at least once. Public work adds a layer. A contractor on a Texas government contract worth at least $1 million has to preserve its contracting information under Government Code Section 552.372 and, at completion, either hand it over or keep it under the agency’s retention schedule. Our guide to IT compliance for Texas contractors covers what each type of contract adds.

10. Decide who takes the 6 AM call

The vendor’s support team answers software questions. It won’t fix a tablet that can’t reach the trailer Wi-Fi, reset a locked Microsoft account, or work out why the ERP sync went quiet. Those calls come early, from the field, before the office opens. Somebody has to own them, and that person needs admin access to your identity provider, your device management tool and your firewalls. Write the name down.

What should you ask the platform vendor before you sign?

Ask these in writing. The answers go straight into your IT plan.

Procore, for what it’s worth, lists ISO/IEC 27001, SOC 1 Type 2 and SOC 2 Type 2 on its trust center. Ask for the reports. Logos prove nothing.

In what order should the IT work happen?

Tie it to the rollout, not the calendar.

1. Before the kickoff call, turn on single sign-on and multifactor authentication and create the break-glass admin
2. Before the app is installed anywhere, enroll every company tablet and phone in device management
3. During the pilot job, test each office and trailer network against the vendor’s domain list and fix mail filtering
4. Before the ERP sync goes live, move every connector to a service account with a named owner
5. Before the second job starts, migrate active projects only and archive the rest
6. Before June 1, run an offline drill at every active site
7. Before the first closeout, sign off the export and retention rule

None of it’s exotic. It’s just easy to skip when the software training is the part everyone’s excited about.

Do you need a managed IT provider for this?

Maybe not. If you’ve got an IT person in-house who already runs Microsoft Entra ID, Intune and your firewalls, hand them this list and they’ll get through it. You won’t need us.

Where it gets thin is the 20-person contractor with no IT staff, which, going by the county numbers above, describes a lot of Houston. That’s our lane. Our team of 42 has moved construction clients off on-premises servers before, including the cloud-first SharePoint and Entra migration we wrote up as a case study. Fully managed IT starts at $138 per user per month, the first-year rate is locked, and there’s a 120-day satisfaction promise. The details are on our pricing page. And if the bigger question is your Microsoft 365 and Azure setup, our cloud services in Houston cover that side.

Questions Houston contractors ask about moving project management to the cloud

What are Procore’s IT requirements?

Can subcontractors sign in through our single sign-on?

Does Procore work on a jobsite with no internet?

How long should a Texas contractor keep project records after closeout?

Should we move old projects into the new platform?

Who should own the company admin account?

Is a construction cloud migration in Houston different from anywhere else?