Guide
Construction software migration checklist
A clean switch comes down to five things: decide what moves and in what form, check how long your old platform keeps your data, cut over right after your last approved pay app, agree how codes and vendors map, and prove every contract ties out before anyone bills from the new system. This is the checklist we walk through with every customer in the free assessment.
Step 1
Decide what moves.
- Which projects: active ones, closed ones for history, or both
- For each tool: live records in the new platform, searchable history, or left behind
- Which financial history matters most: contracts, change orders, pay apps, retainage and payments
- Whether your new subscription includes the tools you need, such as cost management on Autodesk Forma, which comes with Forma Build
- Who signs off the result: usually your controller or accountant
Step 2
Check how long your old platform keeps your data.
Each vendor’s published terms, as of November 2026. Signed agreements can differ, so check your own contract.
| Platform | After your subscription ends | Source |
|---|---|---|
| Procore | Data available on request for 30 days after your final subscription term ends, solely so you can retrieve it. After that it may be deleted. | Subscription and Services Agreement, section 10.5 |
| Buildertrend | Data may remain accessible for one year, on request, in a format Buildertrend chooses and possibly for a fee. After that it may be permanently deleted. | Terms and Conditions, section 14.2 (June 24, 2026) |
| RedTeam | Export on request at no extra fee within 5 days after termination if all fees are paid, for a one-time fee from day 5 to day 30. After 30 days your content may be destroyed. | Master Subscription and Services Agreement, section 8(d) (January 1, 2026) |
| QuickBooks Online | Read-only access for one year after you cancel a paid subscription, with export to Excel or QuickBooks Desktop. | Intuit help article (updated August 5, 2026) |
Checked November 19, 2026. This is a summary of published terms, not legal advice. Plan the move so it’s finished before your old subscription ends.
Step 3
Pick the cutover date.
- Cut over right after your last approved pay app, usually at a month end, so the next pay app starts in the new platform
- Decide what happens to items still open at cutover, such as pay apps under review or pending change orders: finish them in the old system or bring them over as open
- Keep working in the old system until the cutover; the final move is scheduled around your go-live date
- Give your new platform’s admin time for what a migration doesn’t cover: roles, permissions, approval workflows and report layouts
Step 4
Agree how your data maps.
- Cost codes and cost types: keep your structure, or restructure on the way (combine codes, or split one into several)
- Vendors and companies: names to clean up or merge
- Custom fields: which ones to recreate in the new platform
- Users: who gets invited, and when
Step 5
Prove every contract ties out.
Before anyone bills from the new system, compare old and new, contract by contract. This is what JobMigrate’s reconciliation report shows your accountant.
| Check | What to compare, old system next to new |
|---|---|
| Original value | The contract or PO amount before any changes. |
| Approved changes | The total of approved change orders, and the revised value. |
| Billed to date | Work completed and stored materials billed across every pay app. |
| Retainage held | Retainage still held after every release. |
| Paid to date | Payments issued or received, including partial payments. |
| Record counts | How many records each tool holds, so nothing is missing. |
We do all five steps for you. JobMigrate walks through this checklist in your free assessment, handles the move and fixes any difference before you go live. Our guarantee: every total ties out to the penny, or we fix it before you go live.
FAQ
Migration checklist questions.
When is the best time to switch construction software?
Right after a pay app is approved, usually at a month end. Then the next pay app is created in the new platform from the right billed-to-date and retainage. Switching mid-project is fine when the full billing history comes along.
Should we migrate closed projects?
If your team needs to look them up or report on them, yes. Closed projects can come over in full or as reference history, and your quote covers exactly what you pick.
How long does a construction software migration take?
It depends on how much you’re moving. With JobMigrate, your fixed quote comes with a timeline, a pilot project is signed off first, and the final move is scheduled around your go-live date.
Who should sign off on the migration?
Your controller or accountant. They compare the reconciliation report, contract by contract, and sign off before anyone bills from the new system.
What doesn’t move in a construction software migration?
Who-edited-what history, approval workflows and permissions, report layouts, and payroll records. They’re set up fresh in the new platform. Timesheets stay behind too, except from Procore to Autodesk Forma, where each worker’s hours land on that day’s daily report.
Free assessment
We’ll walk through this checklist with you.
Tell us where you’re moving from and to. Your free assessment covers every step, and your quote is fixed before work starts.