FreshBooks works well for service businesses leaving QuickBooks, but sub-accounts get flattened, credit notes become journal entries, and expense payments default to Petty Cash — plan accordingly.
QuickBooks to FreshBooks migration guide for service businesses. Covers CoA mapping, API limits, Petty Cash traps, credit note workarounds, and migration methods.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Do not scope this as a like-for-like accounting replica
The clean version of this migration decides up front which history belongs inside FreshBooks, which balances should come in as opening journals, and which records stay in exported QuickBooks archives for audit and reference.
If your QuickBooks file uses classes, locations, or multi-level sub-accounts for
If your QuickBooks file uses classes, locations, or multi-level sub-accounts for departmental reporting, FreshBooks cannot replicate that reporting structure. You'll need to flatten or abandon those dimensions before migrating.
Always sanitize account names before writing to FreshBooks
Strip & characters and replace : with - in CoA names. This single preprocessing step prevents the most common batch failure.
Test with ugly data, not clean samples
Your pilot set should include one refunded invoice, one partially paid invoice, one reimbursable expense, one vendor bill, one deep sub-account branch, and one account name with special characters.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Scope the ledger, the subledgers and the audit obligations.
Objective Agreed scope across master data, open transactions and historical balances, with finance and audit signed up.
Keep these open
-
Inventory master data and transaction volumes in QuickBooks
Count GL accounts, customers, vendors, items, fixed assets, open AR and AP, and transaction lines by year. Transaction line volume, not header count, is what determines your load time.
Data Profiler Get real record counts instead of estimating from memory -
Decide the history strategy with finance and audit
Choose between opening balances only, open items plus balances, or full transactional history. This is the single biggest scope decision in an ERP migration: full history multiplies effort many times over, and most organisations land on balances plus open items plus a read-only archive.
Full transactional history is rarely worth the cost. Confirm what your auditor actually requires before assuming you need it.
Vendor Evaluator Score FreshBooks against alternatives on weighted criteria -
Consult the external auditor early
The auditor has views on cut-over timing, audit-trail retention and how you evidence that balances carried across correctly. Finding this out after go-live can mean a qualified opinion, so get it in writing now.
-
Review the chart of accounts and decide whether to redesign
A migration is the natural moment to restructure the COA, and also the riskiest one. If you redesign, you need a mapping from old to new for every historical balance, plus a plan to restate comparatives.
Redesigning the chart of accounts mid-migration doubles the reconciliation burden. Treat it as a separate, sequenced project if you can.
-
Catalogue integrations and statutory reporting
List banking feeds, payment gateways, tax filing, payroll, CRM, e-commerce, warehouse and BI. Then list every statutory and tax filing obligation with its deadline — those deadlines constrain your window absolutely.
-
Pick a period-aligned go-live date
ERP cutovers align to a period boundary — ideally the start of a fiscal year, otherwise the start of a clean month. Mid-period cutover means split-period reporting for the rest of the year.
-
Confirm your FreshBooks plan
You need Plus, Premium, or Select for Advanced Accounting and CoA customization. Lite won't work.
-
Decide your historical cutoff
Most service businesses migrate the current fiscal year plus one prior year, then archive the QuickBooks file.
-
Identify credit notes
Count them. Fewer than 20? Manual journal entries post-migration might be faster. Hundreds? Automate.
QuickBooks → FreshBooks specifics
- Time tracking → invoicing pipeline
- Time entries map directly to invoice line items. In QuickBooks, this requires workarounds or third-party apps.
- Project-level profitability
- FreshBooks treats projects as first-class objects with budgets, team members, and billable hours built in.
- Client portal
- Clients can view invoices, approve estimates, and pay online without you emailing CSV statements.
- Simpler pricing
- No per-user payroll add-ons or inventory modules you never touch.
- Recent detail + opening balances
- Move 12–24 months of invoices and expenses, then post older history as cutover journal entries.
Don't move on until
- Chart of accounts and master-data counts confirmed
- History strategy agreed: balances, open items, or full transactional detail
- External auditor consulted on the migration approach
02 Data Audit Reconcile the source before you migrate it — you cannot fix a ledger later.
Objective A source ledger that balances, with master data cleansed and every open item agreed.
Keep these open
-
Produce and sign off a source trial balance
Run the trial balance in QuickBooks and have the controller sign it. This is your migration baseline: without a signed pre-migration position you have nothing to reconcile the target against, and any later discrepancy is unarguable.
Without a signed, dated source trial balance you cannot prove the migration preserved the ledger. Do this before anything else.
-
Reconcile subledgers to the general ledger
Confirm AR, AP, inventory and fixed-asset subledgers tie to their GL control accounts. Pre-existing breaks must be resolved in QuickBooks: migrating an out-of-balance ledger makes the break permanently unattributable.
Data Profiler Profile the QuickBooks export for nulls, outliers and type drift -
Clean and deduplicate master data
Deduplicate customers, vendors and items, and identify records that should not carry forward. Duplicate vendors are also a fraud-control weakness, so this has value beyond the migration.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Agree open AR and AP item by item
Every open invoice, credit note and payment on account needs an owner and an agreed amount, including partially-paid items and foreign-currency balances. Open items are what customers and vendors will dispute in week one.
-
Validate export structure, encoding and precision
Check numeric precision and rounding on the export, and confirm dates and currency codes are unambiguous. Precision loss on amounts is silent, cumulative and produces penny differences that take days to trace.
Amounts exported at reduced precision will not re-total. Verify decimal places before you accept the export.
CSV Validator Catch broken headers and ragged rows in the raw export -
Scan for regulated data and produce masked test data
ERP data holds bank details, tax IDs and payroll information. Scan it, restrict who can see it, and generate a masked copy for the sandbox and for any implementation partner.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Audit your CoA for special characters
Search for & and : in all account names and rename before export.
Don't move on until
- Trial balance in QuickBooks balances and is signed by the controller
- AR and AP subledgers reconcile to the GL control accounts
- Master data deduplicated and inactive records identified
03 Field Mapping Map the COA, the dimensions and the subledger structures.
Objective A signed mapping covering the chart of accounts, dimensions, tax codes and currency handling.
Keep these open
-
Map the chart of accounts account by account
Every source account maps to exactly one target account, or to a documented split with agreed proportions. The controller reviews and signs this line by line — an unreviewed COA map is how a balance sheet stops balancing.
Schema Mapper Match QuickBooks fields to FreshBooks by uploading both schemas -
Map dimensions, cost centres and analysis codes
ERPs differ structurally here: segments, dimensions, tracking categories and classes are not interchangeable. Confirm how FreshBooks models analysis and whether your existing reporting hierarchy survives the translation.
-
Map tax codes, rates and jurisdictions
Map every tax code with its rate, jurisdiction and reporting treatment, then verify the mapping reproduces your last filed return. Tax errors are statutory exposure, not reporting inconvenience.
A tax-code mapping that has not been tested against a previously filed return is untested. Reproduce a real filing before sign-off.
-
Decide multi-currency and exchange-rate handling
Confirm functional and reporting currencies, and how historical rates are stored. Revaluing historical transactions at current rates rewrites reported results and will not tie to filed accounts.
Historical transactions must retain their original transaction-date rates, or your comparatives will not match filed statements.
-
Map master data and subledger structures
Map customer and vendor records with their payment terms, credit limits and tax registrations, and item records with units of measure and costing method. Costing-method differences change inventory valuation, which changes the balance sheet.
-
Set load order and freeze the spec
COA, then dimensions, then master data, then opening balances, then open items, then any historical detail. Version and sign off the spec with the controller before the pilot.
Don't move on until
- Account-by-account COA mapping reviewed by the controller
- Tax codes and jurisdictions mapped and verified against filings
- Multi-currency and rate handling agreed with finance
04 Test Migration Prove the ledger balances in the target before you trust it.
Objective A sandbox load whose trial balance matches the signed source position to the penny.
Keep these open
-
Configure the FreshBooks sandbox with the agreed structures
Build the COA, dimensions, tax codes, currencies, fiscal calendar and posting rules before loading anything. Every one of these affects how a posted transaction lands, so an unconfigured sandbox produces meaningless results.
-
Load master data and validate it
Load customers, vendors and items first and verify counts, payment terms, tax registrations and costing methods. Transactions cannot post correctly against wrong master data, so this gate comes before any balance work.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Load opening balances and prove the trial balance ties
Load opening balances and run a trial balance in FreshBooks, comparing to the signed source position. It must match exactly — a rounding difference here is a mapping defect, not a rounding difference.
Any variance at all between source and target trial balance must be explained line by line. "Close enough" is never acceptable in a ledger.
-
Load open items and reconcile the subledgers
Load open AR and AP with their ageing intact, then confirm subledger totals tie to GL control accounts and that ageing buckets match. Ageing that shifts means transaction dates mapped wrongly.
-
Run a full period-end close in the sandbox
Execute the whole close: revaluation, accruals, depreciation, tax calculation, and financial statement generation. Compare every statement to QuickBooks for the same period. The close is where structural mapping errors finally become visible.
-
Test transactions end to end and reproduce a tax filing
Post a sales order to cash and a purchase order to payment, then generate the tax return for a previously filed period and compare it to what you filed. If both reconcile, the configuration is sound.
-
Run a Trial Balance in QuickBooks
This is your baseline. Compare it against FreshBooks post-migration to verify accuracy.
Don't move on until
- Target trial balance matches the signed source trial balance exactly
- Subledgers reconcile to control accounts in the target
- A full period-end close has been run in the sandbox
05 Cutover Switch the ledger on a period boundary, with balances proven.
Objective Balances and open items live in FreshBooks, transacting resumed, and a signed post-load trial balance.
Keep these open
-
Close the final period in QuickBooks and freeze posting
Complete the period-end close, then lock posting entirely. An ERP freeze is absolute: a single journal posted to the old system after the final export leaves the two ledgers permanently divergent.
One journal posted in the old ERP after the final export breaks the reconciliation permanently. Lock posting at the system level, not by asking people nicely.
-
Publish the cutover runbook with the abort point
A timed, owner-named sequence for load, balance verification, integration switch and go/no-go, with an explicit abort criterion. The trial-balance check is the gate — nothing proceeds until it ties.
-
Load balances and open items into production
Load the final opening balances and open AR/AP into FreshBooks production, following the pilot-proven sequence. Do not improvise the order under time pressure.
-
Reconcile and sign the post-load trial balance
Run the trial balance in FreshBooks and reconcile it to the signed source position, then have the controller sign the result. This signature is your evidence for the auditor and your go/no-go gate.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint banking, payment and tax integrations
Switch bank feeds, payment gateways, tax filing connections, payroll and BI, then process one real low-value payment and one bank reconciliation end to end. Banking errors move real money, so verify with live traffic.
Payment integrations left connected to the old ERP can duplicate real payments. Disable them before switching, not after.
-
Go/no-go, then open for transacting with daily reconciliation
Call the decision on the signed trial balance, open FreshBooks for posting, and reconcile daily for the first two weeks with finance support on hand. Keep QuickBooks read-only for statutory retention — this is an audit requirement, not a preference.
-
Plan your bank feed cutover
When you connect bank feeds in FreshBooks, it pulls 30–365 days of transactions depending on the bank. Disconnect your bank feeds from QuickBooks after your last reconciliation there, and connect them in FreshBooks only when you're ready to go live. If there's overlap between imported bank transactions and migrated historical expenses, you'll need to match or delete duplicates during reconciliation.
Don't move on until
- Post-load trial balance signed by the controller
- Banking, tax and payment integrations verified live
- Users transacting and the first daily reconciliation clean
06 Validation Prove the statements, the tax position and the audit trail.
Objective Financial statements reproducing the source position, a clean tax filing, and auditor acceptance.
Keep these open
-
Reconcile the full ledger and all subledgers
Reconcile trial balance, AR, AP, inventory, fixed assets and bank against the signed source position. Produce a single reconciliation pack that goes to the auditor.
Migration Validation Tool Reconcile QuickBooks and FreshBooks record-for-record -
Reproduce the financial statements
Generate balance sheet, P&L and cash flow in FreshBooks and compare to the pre-migration statements. Every variance needs a documented explanation traced to a specific mapping decision.
-
Complete and review the first period-end close
Run the first real close in FreshBooks with extra review at every step. Compare its duration and outcome to your historical close, and treat anything unexpected as a live finding.
Data Profiler Prove field completeness held up through the load -
Verify the tax position and file
Generate and review the first tax filing from FreshBooks, reconciling it to the underlying transactions before submission. Have the tax lead review it independently.
The first statutory filing out of a new ERP should be reconciled manually to source transactions before submission.
-
Confirm controls, segregation of duties and audit trail
Verify user permissions, approval limits, segregation of duties and audit logging in FreshBooks. Controls do not migrate, and a control gap found by an auditor is far more expensive than one you find yourself.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Obtain auditor acceptance and retain the archive
Walk the auditor through the reconciliation pack, get written acceptance, and retain QuickBooks read-only for the full statutory retention period. Diarise the retention expiry rather than the contract renewal.
Don't move on until
- Financial statements match the pre-migration position
- First period-end close completed and reviewed in FreshBooks
- Auditor satisfied and archive retained for the statutory period
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
Account Type Equivalent
| QuickBooks field | FreshBooks field | Notes |
|---|---|---|
| Bank | Cash & Bank | Created automatically when bank rec opening balance is set |
| Accounts Receivable | Accounts Receivable | Multiple AR accounts in QB merge to one in FreshBooks |
| Accounts Payable | Accounts Payable | Multiple AP accounts in QB merge to one |
| Income | Revenue | All sales invoices code to "Sales" by default |
| Cost of Goods Sold | Cost of Goods Sold | Supported, but no inventory items behind it |
| Expense | Operating Expenses | Categories are expense accounts in FreshBooks |
| Equity | Equity | Owner's draws/investments map directly |
| Other Current Liability | Liability | Sales tax accounts merge to single VAT account |
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate QuickBooks data to FreshBooks automatically?
Yes. FreshBooks' official partner MMC Convert (Easy Switch) handles standard migrations in 48-72 hours. For complex migrations with custom mapping, API-based scripts or an engineered migration service like ClonePartner provide more control over data transformation. A native one-click full-ledger import does not exist.
What QuickBooks data cannot be migrated to FreshBooks?
FreshBooks does not support inventory tracking, classes, locations, purchase orders, multi-currency files, payroll history, budgets, memorized transactions, or customer jobs. Credit notes must be converted to journal entries since common migration methods lack native credit note support. Sales Receipts have no FreshBooks equivalent and are typically migrated as invoices.
Why do expense payments end up in Petty Cash after migrating to FreshBooks?
The FreshBooks API does not allow pushing expenses directly through bank accounts. It defaults all expense payments to Petty Cash as a clearing account. After migration, you need adjustment journal entries or bank reconciliation to move payments to the correct bank accounts.
Does FreshBooks support QuickBooks sub-accounts?
Partially. FreshBooks supports one level of parent/sub-account nesting on Plus, Premium, and Select plans. However, API-based migration methods — including MMC Convert's standard workflow — typically flatten QuickBooks multi-level sub-accounts into independent accounts. You may need to manually rebuild some nesting post-migration.
Can I import my Chart of Accounts into FreshBooks?
No. FreshBooks does not support importing an existing Chart of Accounts from another source. You must customize the target CoA manually in FreshBooks, and beginning balances are added via journal entries. CoA customization requires Plus, Premium, or Select plans.