Construction ERP managed IT support covers everything underneath the ERP application. The server, the SQL database, the sync agents, the field connection, and the restore. Your ERP vendor supports the software. Nobody ships with the rest.
That’s the whole argument. It takes about 4 minutes to explain why it costs contractors real money, and if you already run IT for a Texas construction company, you’ve probably lived some version of it already.
Sage 300 CRE, Viewpoint Vista, CMiC, and Acumatica all sit on top of a Windows server, a SQL database, a sync service, and a network path from the job site. Your ERP vendor supports one of those layers. Your reseller supports the configuration. The other four belong to whoever you hired last. When the system goes down on payroll week, the finger pointing starts, and the clock keeps running.
What does a managed IT partner do for a construction ERP?
A managed IT partner owns the infrastructure your ERP runs on. That means patching the Windows server and the SQL instance, monitoring the sync services that move data between the ERP and Procore, securing remote access for field staff, backing up the database at a tested restore point, and holding one ticket queue when something breaks.
Notice what’s missing from that list. Nobody’s touching your chart of accounts. Nobody’s redesigning your job cost structure either, because those belong to your controller and your ERP consultant, and they should stay there.
So where does the confusion come from? When you bought the ERP, somebody said they’d support it. They meant the application. They did not mean the box. Big difference.
What is actually in a construction ERP stack?
Pull apart a typical Sage 300 CRE install at a $40M general contractor and you’ll find 6 or 7 distinct pieces of technology, each with a different owner, each with a different renewal date, and almost none of them written down anywhere in one place.
| Layer | What it looks like in a construction shop | Who actually owns it |
|---|---|---|
| ERP application | Sage 300 CRE, Vista, Spectrum, CMiC, Foundation | Software vendor plus your reseller |
| Configuration and workflow | Job cost structure, AIA billing setup, certified payroll templates | Your ERP consultant and your controller |
| Database engine | Microsoft SQL Server or Actian Zen, depending on version and module | Nobody, in most shops |
| Server operating system | Windows Server, physical or virtual, patched or not | Nobody, in most shops |
| Integration services | The hh2 sync client, API connectors, scheduled imports | Split, badly |
| Access path | VPN, RDS or Citrix session, jobsite internet, cellular failover | Whoever set up the office network |
| Backup and restore | Database backups, tested restores, offsite copy, recovery time | Assumed, rarely verified |
Count the rows that say “nobody.” There are three. That’s not an exaggeration for effect, it’s what I find in most vCIO assessments at contractors between 30 and 300 employees, and the pattern holds whether the company runs one office or nine.
Trimble is refreshingly honest about this in its own documentation. A self-hosted Viewpoint Vista deployment expects you to bring Windows Server, SQL Server, .NET, and the reporting dependencies. They sell a hosted option for a reason. Plenty of contractors would rather not own any of that.
Vendor supported does not mean Microsoft supported
Here’s the trap. It catches more contractors than anything else on this page, and almost nobody in the industry talks about it.
Sage’s published requirements for Sage 300 CRE versions 24 and 25 list Windows Server 2016 through 2022 as supported, with Server 2025 added in version 25.2. Sage Paperless Construction needs SQL Server 2016 SP3 or newer. Read those as a floor. Not a recommendation.
Because Microsoft already moved.
| Component | Microsoft support ends | Status as of August 2026 |
|---|---|---|
| SQL Server 2016 | July 14, 2026 | Already unsupported. Security updates require paid ESU |
| Windows Server 2016 | January 12, 2027 | Roughly 5 months out |
| Windows Server 2019 | January 9, 2029 | Safe for now, but plan the hardware refresh |
So a contractor can be running a fully current, fully vendor-supported version of Sage 300 CRE on a database engine that Microsoft stopped patching on July 14, 2026. Both things are true at the same time. Your ERP vendor has no reason to call you about it, and the reseller who ran your implementation back in 2019 is not watching Microsoft’s lifecycle calendar on your behalf either.
Windows Server 2016 is next in line. January 12, 2027. If your ERP server was built in 2017 or 2018, go look at it today. Not next quarter.
5 ways a construction ERP breaks when nobody owns the infrastructure
None of these are hypothetical. They’re the recurring pattern across construction engagements, roughly in order of how often they show up.
The sync agent quits and job costs quietly stop moving
Run the Procore connector to Sage 300 CRE and there’s a Windows application sitting on your Sage server doing the work. Procore documents it plainly. The hh2 Synchronization Client installs on the Sage 300 CRE server, requires .NET Framework 4.8 or higher, and holds an outbound connection over ports 80 and 443. Restrict outbound traffic on your firewall and two specific IP addresses have to stay allowlisted or the whole thing goes quiet.
Picture what happens when that service stops. No alarm sounds in accounting. Commitments stop flowing, job costs go stale, and project managers keep reading numbers that were accurate 9 days ago while making buyout decisions against them. Somebody notices at month end. Usually the controller. Nine days of stale numbers is a lot of buyout.
A monitored server catches a stopped service in minutes. An unmonitored one catches it in a WIP meeting.
The database sits on a server that stopped getting patches
Covered above, so I’ll keep this short. Ask your team one question. Who applied the last security update to the ERP server, and on what date? If producing that answer takes more than 30 seconds, you already have your answer.
Field access rides on a VPN nobody has tested since setup
Jobsite trailers take whatever internet is available. Fixed line if the site’s mature. Cellular if it isn’t. Superintendents pulling drawings and submitting time run through a VPN or a published desktop session that somebody configured once, years ago, and hasn’t touched since.
Then a certificate expires. Or the ISP swaps the modem and the static IP changes. Or the firewall firmware finally gets updated and the old tunnel config no longer negotiates, and field staff lose ERP access on a Tuesday morning while the office finds out through a phone call instead of an alert. We wrote up a close cousin of this in a Texas construction cloud migration case study, and connectivity shows up again in our rundown of IT risks on Texas job sites. Different symptom, same root cause. The infrastructure assumed everybody worked in one building.
Backups protect the files and miss the database
This one scares me most. It looks fine on a report.
File-level backup software copies the folder where SQL keeps its data files, but the database is open and in use while that copy runs, so what lands in the backup set is an inconsistent snapshot that restores as a corrupt database or refuses to restore at all. You find out on the worst possible day. Every time.
Proper protection means SQL-aware backups with transaction log handling, an offsite copy, and a real test restore on a schedule somebody signs off on. Our Texas disaster recovery practice treats an untested restore as no backup whatsoever. Functionally, that’s exactly what it is.
The outage lands on payroll week
ERP outages aren’t equal. Lose the system on a Wednesday mid billing cycle and it hurts. Lose it during payroll processing on federal work and you have a legal problem, which I’ll get to shortly.
How exposed is construction to ransomware right now?
Threat data got noticeably worse for contractors over the last 18 months. The reason isn’t mysterious. Construction firms hold banking details, subcontractor records, bid documents, and lien information, and as a sector they’ve historically underinvested in security relative to the size of the money moving across their balance sheets.
GuidePoint Security’s GRIT team counted 131 construction ransomware victims in Q1 2026. That’s up 44% year over year. It moved construction to 4th among all industries, behind only manufacturing, technology, and healthcare, and 22 separate threat groups claimed construction victims inside that single quarter. Four of them account for 55% of the total. Qilin, Play, Akira, and DragonForce.
Your ERP server is the highest-value target sitting on your network, because it holds job costs, vendor banking details, payroll history, and the accounting data that actually runs the business day to day. If it also happens to be the least patched machine you own, you have built half the attack for them. Free of charge.
The certified payroll clock does not pause for an outage
Federal and federally assisted work carries a weekly filing obligation. Under 29 CFR 3.4, each certified payroll has to reach the contracting agency within 7 days after the regular payment date for that payroll period. Form WH-347 is how most contractors handle the paperwork. Texas contractors on TxDOT federal-aid projects and federally funded municipal work live inside that rule every single week of the year. No exceptions.
Your ERP generates those reports. A 3-day outage during payroll week isn’t an IT inconvenience, then. It’s a compliance event with a paper trail, on a project where the contracting agency reviews every submission you send.
That’s the argument I use with construction CFOs who file managed IT under overhead. It isn’t overhead. It’s what stands between a server failure and a late certified payroll filing on a federal job.
Why most Texas contractors can’t solve this with a hire
Hiring someone seems like the obvious answer. Here’s why the math rarely works.
Texas averaged 65,325 private construction establishments across 2025, employing 901,391 people, according to BLS Quarterly Census of Employment and Wages data. Divide it out. The average Texas construction establishment runs 13.8 people. Statewide construction employment reached 921,700 in July 2026, so the sector keeps growing, but the individual firms stay small.
A 14-person contractor is not hiring a SQL DBA. Neither is a 60-person one. Even at 200 employees, the one IT person you hire will be genuinely excellent at one of the 7 layers in that table above and guessing at the other 6, because no single human being is simultaneously a Windows admin, a database administrator, a network engineer, a security analyst, and a backup specialist.
Which is why co-managed IT fits construction unusually well. Your internal person keeps the ERP relationships, the user training, and the operational knowledge that only comes from being in the building. Specialists cover the infrastructure layers. Nobody gets asked to be 5 people. That is the whole idea.
What should you fix in the next 90 days?
You don’t need a transformation program. You need to close specific gaps in a specific order. If you are still choosing who does that work, our scored comparison of construction IT providers in San Antonio shows which firms document ERP support and which only claim it.
- Write down every layer. Server name, OS version, SQL version, ERP version, and every integration service running on that box. One page. Most contractors have never done this.
- Check the two Microsoft dates. If SQL Server 2016 or Windows Server 2016 shows up anywhere, that’s your first project, and it carries a deadline you didn’t set.
- Test a restore. Not a backup report, an actual restore of the ERP database into a spare environment, timed, with the controller confirming the data came back right.
- Alert on the sync services. Every integration agent should page somebody the moment it stops. Takes about an hour to configure.
- Put multifactor on remote access. Every VPN account, every published desktop, no exceptions for the owner.
- Name one owner. One vendor, one number, one person accountable when the ERP is down and it isn’t obvious whose fault it is.
Step 6 does more work than the other 5 combined. Technical gaps are fixable in a weekend. Ownership gaps stay open for years. Sometimes decades. The work in steps 1 through 5 is a weekend of effort for somebody who does it professionally, but step 6 is an organizational decision, and organizational decisions have a way of sitting in a folder through three budget cycles.
How Uprite supports construction ERP environments in Texas
We handle the infrastructure layer under Procore, Sage 300 CRE, Viewpoint Vista and Spectrum, Bluebeam Revu, Buildertrend, and HCSS for contractors across Houston, Dallas, Fort Worth, San Antonio, and Austin. Not the chart of accounts. The servers, the databases, the sync services, jobsite connectivity, and the restore. That’s the line.
Our construction practice runs on the Uprite BUILD framework, which comes in 4 tiers so the fit matches how you’re already staffed. BUILD Complete for contractors with no internal IT. BUILD rComplete for remote-first support. BUILD Impact for co-managed shops that already have an internal admin, and BUILD Secure for the compliance and vCISO layer that federal and defense work tends to demand. A 42-person team covers it, which is the practical reason we can point a Windows admin, a database specialist, and a security analyst at one contractor’s environment without any of them being the same person.
Want the short version of what to do next? Get an assessment of your ERP environment. We document all 7 layers, flag your end-of-support exposure, and test whether the database actually restores. Start with construction IT services in Houston or the statewide managed IT services overview, then book the assessment.
Questions Texas contractors ask about ERP support
Doesn’t our ERP reseller already cover this?
Almost never. Resellers implement and configure the ERP application, train your staff, and handle version upgrades. Server patching, database maintenance, backups, network security, and remote access all sit outside that scope. Pull your support agreement and search it for the word “infrastructure.” It usually isn’t in there.
Can we move the ERP to the cloud and skip all of this?
Cloud hosting removes some layers, not all of them. Trimble and CMiC both offer hosted deployments that take the server and the database off your hands, which genuinely helps. You still own identity, endpoint security, jobsite connectivity, every integration, and every device that touches the system. Smaller problem. Not a solved one.
What does construction ERP managed IT support cost?
Most Texas contractors land between $125 and $225 per user per month for full coverage. Server and infrastructure counts move that number more than headcount does. Co-managed arrangements run lower because your internal person absorbs the frontline tickets. Our construction IT pricing breakdown works the per-seat math in detail. Ask for a fully loaded quote that includes the ERP server, not just the desktops.
Our ERP has run fine for 6 years. Why change anything?
Fair challenge, and sometimes the honest answer is that you shouldn’t. But 6 years of uptime on an unpatched server isn’t evidence of good design. It’s evidence you haven’t been targeted yet. Check the two Microsoft support dates first. If neither one applies to you, your risk really is lower than most.
Who fixes it when Procore and Sage stop talking to each other?
Depends entirely on where the break is, which is precisely the problem. Procore supports its side of the connector. Sage supports the ERP. The hh2 sync client running on your server belongs to neither of them, so a managed IT partner who owns the server, the service, and the firewall rule can triage in one place instead of three.
Do we still need our internal IT person?
Keep them. Internal staff carry context nobody outside the company can replicate, including which superintendent needs hand-holding and which jobsite has the bad circuit. Co-managed models pair that knowledge with specialists for the infrastructure layers. The failure mode we see is one internal generalist asked to cover all 7 layers alone.
