Pick the cutover date
Cut over at a period end, ideally a fiscal year end or at least a quarter end that has been closed and reviewed. The last closed period in QuickBooks becomes the opening balance in the new system, and every later transaction is entered only once, in the new system. Avoid cutting over mid-month: a split month means two systems both claim part of the same period and neither reconciles.
- Close the final QuickBooks period fully: bank recs done, AP and AR aged, WIP schedule prepared and reviewed
- Freeze master data changes (new vendors, customers, cost codes) two weeks before the date
- Plan for a short parallel period on a handful of transactions, not a full double-entry month
- Keep the QuickBooks file read-only for history; do not re-enter historical transactions
What to bring, what to leave
| Bring | Leave in QuickBooks |
|---|---|
| Chart of accounts, mapped to the new structure (not copied as-is) | Inactive accounts and one-off accounts created for workarounds |
| Active customers, vendors and employees, de-duplicated | Inactive names and duplicate vendors with slightly different spellings |
| Opening trial balance as of the cutover date | Historical journal detail, unless comparative reporting requires a year |
| Open AR and AP items with their original dates | Paid and closed documents |
| Open jobs with budgets by cost code, cost to date and approved changes | Closed jobs (keep a summary for reference) |
| Open subcontracts and purchase orders with amounts billed to date | Fully billed commitments |
| Retainage receivable and payable by job, and by line where the contract requires it | Retainage that has already been released and paid |
| Schedule of values and billed-to-date for every open contract | Old pay applications, except the last certified one per job |
The sequence
- Set up the organization: fiscal calendar, chart of accounts, dimensions (jobs, phases, cost codes), roles and approval limits
- Import master data: customers, vendors, employees. Review duplicate matches before committing
- Create open projects with budgets by cost code, approved change orders and the current contract value
- Enter open commitments (subcontracts and POs) with amounts billed to date so remaining commitment is right
- Load open AR and AP as individual items with original dates, not a single balance per customer or vendor
- Load retainage receivable and payable by job so the first release can be traced
- Enter the schedule of values and last certified pay application per contract so the next application continues the sequence
- Post the opening trial balance as one journal dated the cutover date; subledger control accounts must equal the loaded open items
- Enter and approve the opening cost-to-complete forecast for each open job
- Produce the first WIP schedule from the new system and tie it to the last one from QuickBooks
The tie-outs that prove it
Each tie-out compares a number from the new system to the same number from the final QuickBooks period. A difference is either a known mapping decision, written down, or an error to fix before go-live. Sign-off means every line below has a matching figure or a documented reason.
| Tie-out | New system | Last QuickBooks period |
|---|---|---|
| Trial balance | Opening journal, every account | Closing trial balance |
| AR control | Sum of open customer items | AR aging total |
| AP control | Sum of open vendor items | AP aging total |
| Retainage receivable and payable | Sum by job | Retainage balances by job (often a spreadsheet) |
| Job cost to date | Per job and per cost code | Job profitability report, with the spreadsheet adjustments you were making |
| Open commitments | Remaining per subcontract and PO | Commitment log |
| Billed to date per contract | Schedule of values | Last certified pay application |
| WIP schedule | Earned, billed, over/under per job | Last WIP schedule |
Common cutover mistakes
- Copying the QuickBooks chart of accounts instead of mapping it, so the workaround accounts live on forever
- Loading a single opening balance per customer instead of open items, so the first aging report is wrong and cash application has nothing to apply against
- Opening job cost entered as one lump per job, with no cost code detail, so the first forecast has nothing to work from
- Retainage balances left inside AR and AP instead of in their own accounts
- Commitments entered at original value without billed-to-date, so remaining commitment doubles
- Skipping the opening forecast, so the first WIP schedule runs with no estimate at completion
- Running both systems in full for a month “to be safe”, which guarantees they disagree and nobody knows which is right
How Forge ERP handles cutover
Forge’s setup has a cutover plan with the generic tasks and, for construction organizations, a vertical task list: map and import open projects, phases and budgets; map open commitments and subcontract terms without duplicating AP; load open vendor applications, retainage and compliance references; reconcile job cost, commitments, retainage, AIA billing and WIP; and approve current forecasts before go-live. The construction reconciliation scope is explicit: job cost and commitment exposure to the source system, AP and AR retainage to subledger and GL, and AIA billing and cumulative WIP to approved source snapshots.
The data import wizard accepts QuickBooks Online, Xero, Sage Intacct and NetSuite exports for trial balances, vendors, customers and employees, and any other CSV through column mapping, with downloadable column templates. Every import is staged and validated before it commits; vendor and customer imports go through duplicate matching rated low, medium or high for review; an import can be rolled back completely; and a trial balance posts as a draft journal dated the cutover date that you review before posting. Vendor bank details are fingerprinted on import rather than stored in the clear, and credentials and secret keys are excluded from cutover scope.
Forge ERP covers projects, purchasing, accounts payable, billing and receivables, job cost and WIP, reporting and close. Payroll runs in your payroll provider and lands in Forge as job-costed labor with burden. Forge is in beta with a 14-day free trial.
Frequently asked
- How long does a QuickBooks-to-ERP cutover take?
- For a contractor with clean books, the data work is typically a few weeks around a period end: two to three weeks of preparation and mapping, the cutover weekend, and one to two weeks of tie-outs. Dirty master data and undocumented retainage are what stretch it.
- Do I need to bring historical transactions?
- Usually not. Opening balances and open items are enough to operate. Bring prior GL detail only when comparative reporting requires it; otherwise keep the QuickBooks file read-only for lookups.
- Should I run both systems in parallel?
- A short parallel on a sample of transactions is useful to confirm mappings and approvals. A full parallel month is not: it doubles the work and the two systems will disagree in ways that take longer to explain than the parallel saved.