Migration path
Procore to Autodesk Forma migration
Yes, you can move your full Procore history into Autodesk Forma (formerly Autodesk Construction Cloud, or ACC). JobMigrate recreates each Procore record in the matching Forma tool: budgets, contracts and change orders, every pay app with its retainage and payments, plus RFIs, submittals, drawings, documents and field records. Then we prove every total with a reconciliation report.
The short answer
Procore tool by tool, one to one where Forma has a match.
The same records, numbers, statuses, dates and files you had in Procore, in the Forma tool built for them. Where Forma works differently, you know before anything moves.
- What moves
- 25 Procore tools land as live records in Forma, including every pay app with retainage, stored materials and payments.
- Where it lands
- Financials in Forma Build’s Cost Management, RFIs, submittals and field records in Forma Build, and files and drawings in Forma Data Management.
- Who does the work
- We do. You give us an admin login in Procore and in Forma, and nobody on your team has to set anything up first.
- What Forma changes
- Forma shows our admin user and the day of the move as who created, submitted or approved each record. The original names and dates stay on the record and in its Procore PDF.
- Price
- One fixed, one-time fee based on how many records you move. No subscription, no per-user fees.
- Proof
- A reconciliation report: every budget, contract, change order, pay app and payment total, Procore next to Forma.
What moves
Each Procore tool we move, and where it lands in Forma.
Where each tool lands in Forma, and whether it lands exactly as it was.
1:1 lands as it was1:1 with notes lands complete; Forma shows it a little differently
| Procore tool | Forma tool | Result | What lands |
|---|---|---|---|
| Financials | |||
| Budget | Cost Management budget | 1:1 | Cost codes, original budget and approved changes, including codes shared by several contracts. |
| Prime contract | Main contract | 1:1 | Schedule of values line by line, with retainage terms. |
| Subcontracts and POs | Contracts | 1:1 | Schedule of values, retainage, vendor and status, whether open, part-billed or closed out. |
| Change orders | Change orders | 1:1 | Owner and subcontract side, approved, pending or void, line by line on the right contract. |
| Subcontractor invoices | Payment applications | 1:1 with notes | Every period: work, stored materials, retainage held and released, and status. Same amounts; Forma figures stored-material retainage its own way, so the Procore invoice is attached. |
| Owner invoices | Payment applications | 1:1 | Every period, with amounts and status. |
| Payments | On each pay app | 1:1 | Paid and received, with check number, original paid date and partial payments. |
| Direct costs | Expenses | 1:1 | Invoices, expenses and payroll costs (if entered in Procore), on the right cost code and vendor. |
| Project management | |||
| RFIs | RFIs | 1:1 with notes | Open, closed and draft: number, status, question, due date, location and the official answer with its file. Extra replies come in as comments. Forma marks cost and schedule impact yes or no, so we add the $ amount and days to the RFI. |
| Submittals | Submittals | 1:1 | Spec numbering, type, responses, sent and returned dates, and every revision. |
| Specifications | Specifications | 1:1 with notes | Your spec book, split into sections. Section numbers are also set up for submittals. |
| Meetings | Meetings | 1:1 with notes | Date, location, topics, items, minutes and item status. Each item’s owner and due date go in the item text. |
| Schedule | Schedule | 1:1 | Tasks, WBS, dates and % complete, from your MS Project or P6 file. |
| Field | |||
| Punch list | Issues: punch list | 1:1 | Status, due date, location and description. |
| Observations | Issues: observation | 1:1 | Status, due date, location and type. |
| Coordination issues | Issues: coordination | 1:1 | Status, location and description. |
| Incidents | Issues: safety | 1:1 with notes | Forma has no Incidents tool, so each incident becomes a safety issue with its date and details. |
| Instructions | Issues: general | 1:1 with notes | Forma has no Instructions tool, so each instruction becomes an issue. |
| Inspections | Forms | 1:1 | Every answer (pass, fail, N/A, text, numbers, dates), location, open or closed, on matching templates. |
| Daily log | Forms: daily report | 1:1 with notes | One report per day: crews, equipment and deliveries as report entries, every other entry as text, plus the original Procore daily log PDF. |
| Timesheets | Forms | 1:1 with notes | Each worker’s hours for the week in a time sheet form (Forma has no timesheet tool), by day, regular and overtime apart, with cost code, time type and billable. The hours also show on that day’s daily report. Payroll costs move as direct costs. |
| Documents | |||
| Documents | Files | 1:1 | The same folder tree, with every file. |
| Drawings | Sheets | 1:1 with notes | Every set, sheet and revision lands in Sheets. Sheets that had markups also come as a PDF with those markups, as they were at cutover, in Files. Markups can’t be recreated as editable Forma markups. |
| Photos | Photos | 1:1 with notes | Albums, photos and the date each was taken. Captions don’t carry over to Autodesk Forma Photos. To keep them, photos go to Files instead, each with its caption. |
| Locations | Locations | 1:1 | Your building, floor and area list, still tagged on each record. |
| Procore record | In Forma | Result | What you get |
|---|---|---|---|
| Nothing left behind | |||
| T&M tickets | Files | As history | A PDF and spreadsheet of every ticket. |
| Other forms, such as permits | Files | As history | Searchable PDFs. Inspections move as live forms. |
| Emails, correspondence and transmittals | Files | As history | Searchable PDFs. |
| Estimates and bids | Files | As history | Spreadsheets and PDFs, for reference. |
| Saved reports | Files | As history | The data behind your reports, as Excel files. |
| Full Procore backup | Handed to you | As history | Everything we pull from Procore, in one archive you keep. |
| Edit log (who changed what) | — | Not moved | Procore’s line-by-line edit log stays in Procore. Each record’s final Procore PDF comes along, and Forma keeps its own log from day one. |
| Approval workflows | Set up in Forma | Not moved | Records waiting mid-approval are flagged in your assessment, and you pick the Forma status for each. Finished records keep their final status, like Approved. RFI reviewers are set for you. |
| Custom fields | We create them | Setup | Each custom field you use, and where, is in your quote, priced and selected. We recreate it in Forma and fill every value, or you untick it. |
Every tool is confirmed for your projects in the free assessment. We check what you actually use in Procore and list any Forma difference for your data before you commit to anything.
Before you move
Where Forma works differently, you’ll know first.
Forma has a few rules of its own. We list every one that touches your projects in the assessment, and nothing changes without your OK.
Where Forma works differently
- Who did it, and some dates, show the move. In Forma, moved records show our admin user as who created, submitted or approved them, and Forma doesn’t let anyone change that. Forma also sets change order approval dates, contract executed dates, pay app submitted and approved dates, RFI and issue created and closed dates, and file upload dates to the day records are loaded. The original names and dates stay on the record, in its Procore PDF and in the reconciliation report. Paid dates, award dates, expense dates, submittal dates and drawing issue dates carry over as they are.
- One pay app per contract per billing period. If a subcontract has two Procore invoices in the same month, Forma needs them in separate billing periods or merged into one. We agree which with you before loading.
- Stored-materials retainage. Same amounts; Forma figures retainage on stored materials its own way. The Procore invoice is attached to each of those pay apps.
- Budget codes shared by several contracts. By default Forma lets a budget code belong to one contract. On each project that needs it, we turn on Forma’s project setting that allows more than one; your other projects are unchanged. Once a code is shared, that project’s setting can’t be turned back off, and your team picks the contract each time they charge that budget.
- Forma Build, not Essentials. Budgets, contracts, change orders and pay apps live in Cost Management, which comes with Forma Build. Forma Build Essentials, launched in March 2026 for smaller teams, covers field work such as punch lists and daily reports.
What stays behind, or needs your team
- Procore’s edit log. Who changed what, line by line, stays in Procore. Forma keeps its own log from day one.
- Approval rules and permissions. Set up in Forma after the move. Records waiting mid-approval are flagged in your assessment, and you pick the Forma status for each. RFI reviewers come set for you.
- Report layouts. The data behind your saved reports comes along as Excel files. Budget views and snapshots are set up again in Forma. Forecast numbers move: each budget line’s estimated cost at completion matches Procore.
- An admin login in Procore and in Forma. That’s all we need. We approve our own access and create custom fields ourselves; custom fields are listed and priced one by one in your quote.
Files and access
Documents, drawings, versions and permissions.
Files arrive where your team expects them, and every attachment stays on the record it belongs to.
Files and drawings
- Documents: the same folder tree with every file. Forma records the move as each file’s upload date and author. Older versions of a document can come over too; we confirm which you need in the assessment.
- Drawings: Every set, sheet and revision lands in Sheets. Sheets that had markups also come as a PDF with those markups, as they were at cutover, in Files. Markups can’t be recreated as editable Forma markups.
- Specifications: your spec book loads into Forma’s Specifications tool, split into sections, and the section numbers are set up for submittals.
- Photos: every photo in its album, with the date taken. Captions don’t carry over to Autodesk Forma Photos. To keep them, photos go to Files instead, each with its caption.
- Attachments: every file on a contract, change order, pay app or expense lands on the matching Forma record.
People and permissions
- Roles and access: Procore permission templates don’t carry over, so roles are set in Forma. RFI reviewers are set for you.
- Custom fields: your quote lists each one you use and where, priced and selected. We recreate it in Forma and fill every value, or you untick it.
- Your full Procore backup: everything we pull from Procore, in one archive you keep.
How it works
From free assessment to sign-off.
A clear scope, a fixed price and proof at the end. Your team keeps working in Procore until the cutover.
-
01
Free assessment
You add a JobMigrate user to your Procore company. We review the projects in scope and confirm, tool by tool, what moves and what Forma shows differently.
Free, no commitment -
02
Fixed quote
One price for the whole move, based on your volume, with a timeline. No subscription, no per-user fees.
Price locked before we start -
03
Mapping session
We agree cost codes, vendors, custom fields and your cutover date, usually right after your last approved Procore pay app.
About 1–2 hours of your time -
04
Move & prove
We move one pilot project first for your sign-off, then the rest, and hand you the reconciliation report and your Procore backup.
Signed off by your accountant
Pricing
One fixed fee. No subscription.
You switch platforms once, so you pay once. Your price is fixed before any work starts.
One-time fee
Pay once.
A fixed price, quoted after your free assessment and based on how many records you move, mainly contracts, change orders, invoices and direct costs. $0 per month, per user, forever.
- Free assessment of your Procore projects
- Mapping session: cost codes, vendors, custom fields
- Every pay app with retainage and payments
- Every attachment, linked to the right record
- Reconciliation report for your accountant
- Your full Procore backup, yours to keep
Option A
Start fresh
Carry over open balances and leave the history in Procore, which you keep paying for just to look things up.
Option B
Re-key it by hand
Weeks of your team’s time on data entry, and totals that never quite tie out.
The better option
JobMigrate
Your full history, moved for one fixed fee and reconciled to the penny.
FAQ
Procore to Forma questions.
Is Autodesk Forma the same as Autodesk Construction Cloud (ACC)?
Yes. Autodesk renamed Autodesk Construction Cloud to Autodesk Forma on March 24, 2026. Autodesk Build is now Forma Build and Autodesk Docs is now Forma Data Management, and Autodesk says URLs, logins, APIs and integrations didn’t change. A Procore to ACC migration and a Procore to Forma migration are the same move.
Can pay apps with retainage move from Procore to Autodesk Forma?
Yes. Every subcontractor and owner pay app comes over period by period, with work completed, stored materials, retainage held and released, status, and payments with check numbers and paid dates. Forma allows one pay app per contract per billing period and sets approved dates to the day of the move, so we agree those cases with you before loading.
Do we need Forma Build, or is Forma Build Essentials enough?
For financial history you need Forma Build: budgets, contracts, change orders and pay apps live in Cost Management, which isn’t part of Forma Build Essentials. Files and drawings land in Forma Data Management.
Will our original dates survive the move?
Most do. Paid dates, contract award dates, expense dates, submittal dates and drawing issue dates carry over. Forma sets change order approval dates, contract executed dates, pay app approved dates, RFI and issue created and closed dates, and file upload dates to the day of the move. We keep each original on the record, in its Procore PDF and in the reconciliation report.
How do you get our data out of Procore?
You add a JobMigrate user to your Procore company, and we pull your data ourselves, with your permission. Your team doesn’t export or re-key anything, and you get everything we pulled as one archive you keep.
Can we switch in the middle of a project?
Yes, and that’s where history matters most. We plan the cutover right after your last approved pay app, usually at a month end, so the next pay app is created in Forma from the right billed-to-date and retainage.
How much does a Procore to Forma migration cost?
It’s a fixed, one-time fee quoted after a free assessment, based on how many records you move: mainly contracts, change orders, invoices and direct costs. Vendors, cost codes, attachments, the mapping session and the reconciliation report are included. There’s no subscription and no per-user fee, and the price is locked before work starts.
What happens to our Procore account after the move?
Keep it until you’ve signed off the reconciliation report. Under Procore’s standard subscription agreement, your data is available on request for 30 days after your final subscription term ends, so check your own contract dates. See what happens to your Procore data when you cancel.
Free assessment
See exactly what moves from your Procore projects.
Tell us which projects you’re moving. We check access, confirm tool by tool what lands in Forma, and send a fixed, one-time quote.