FreeAgent lacks a QuickBooks importer. Migration requires manual CSV uploads, precise VAT opening balances (locked after first filing), and separate CIS deduction setup — or API scripting to preserve data relationships.
There is no native migration path from QuickBooks Online to FreeAgent. No importer, no migration wizard, and no supported third-party tool treats FreeAgent as a destination. Movemybooks and Dataswitcher both only work in the opposite direction. QuickBooks Online is a flexible double-entry ledger. FreeAgent is built around the UK tax calendar, enforcing strict rules on how transactions affect Self Assessment, VAT, and CIS. This architectural gap means data cannot be copied — it must be restructured. Migration requires manual CSV uploads, precise VAT opening balance configuration (which locks permanently after the first MTD filing), separate CIS deduction setup, and inventory revaluation from weighted-average to FIFO costing.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
If someone tells you Movemybooks or Dataswitcher can move your QuickBooks data into
If someone tells you Movemybooks or Dataswitcher can move your QuickBooks data into FreeAgent, they are wrong. Both tools treat FreeAgent only as a source platform, not a destination.
FreeAgent's bank CSV import is extremely rigid
FreeAgent requires exactly three columns: column A - date in a specific format only, column B - the Amount, column C - the Description. Unlike QuickBooks Online, FreeAgent does not let you map custom columns during upload. If your QuickBooks CSV export has separate debit/credit columns, split transaction references, or header rows, the upload will silently fail.
Best practice
Time your migration to coincide with the start of a new VAT quarter. This eliminates the mid-quarter split problem and gives you a clean trial balance to import. Moving data at either your year-end or the end of a VAT quarter makes the process much easier. If contractor-side CIS is the bigger risk, the 6th of a tax month can reduce split-period cleanup — that's operational advice, not an HMRC rule.
If you import opening balances and the debits and credits do not match, FreeAgent will
If you import opening balances and the debits and credits do not match, FreeAgent will show the difference and create a Suspense Account entry. That is a migration smell, not a harmless warning. Fix the trial balance before go-live. (support.freeagent.com)
Getting the initial CIS balance wrong has direct HMRC consequences
This figure flows into RTI submissions. If you under-report CIS deductions, you'll overpay tax. If you over-report, HMRC will flag the discrepancy. Pull the exact YTD CIS deduction total from QuickBooks before migrating.
FreeAgent's stock functionality is not available for unincorporated landlord accounts or
FreeAgent's stock functionality is not available for unincorporated landlord accounts or businesses preparing accounts on a cash basis. If you carry minimal stock (common for sole trader subcontractors), a clean opening position is straightforward. If you have significant inventory, consult your accountant about the valuation method change and its tax implications before migrating.
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 FreeAgent 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.
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
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 Opens pre-loaded with the QuickBooks → FreeAgent field pair -
Map dimensions, cost centres and analysis codes
ERPs differ structurally here: segments, dimensions, tracking categories and classes are not interchangeable. Confirm how FreeAgent 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 FreeAgent 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 FreeAgent, 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.
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 FreeAgent, 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 FreeAgent 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 FreeAgent 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 FreeAgent 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.
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 FreeAgent record-for-record -
Reproduce the financial statements
Generate balance sheet, P&L and cash flow in FreeAgent 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 FreeAgent 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 FreeAgent, 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 FreeAgent. 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 FreeAgent
- Auditor satisfied and archive retained for the statutory period
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Contacts (Customers & Suppliers) | low | CSV import supported with a 14-column template, but address fields must be manually split from QBO monolithic blocks. |
| Opening Balances (Trial Balance) | medium | Importable via CSV template, but every QBO account must be manually mapped to FreeAgent nominal codes. Imbalances create a Suspense Account entry. |
| Bank Transactions | medium | CSV import works but the format is extremely rigid. Duplicate detection based on date, amount, and description can behave unexpectedly. |
| VAT History | high | Does not transfer. Opening VAT balances must be entered manually and lock permanently after the first MTD filing. |
| CIS Deductions | high | Year-to-date CIS totals must be manually entered and are filed to HMRC via RTI. Errors directly affect tax liability. |
| Sales Invoices & Bills | high | No native CSV import exists. Historical invoices require third-party tools or FreeAgent API scripting to preserve line items and payment links. |
| Recurring Transactions | high | No import path. All recurring invoices, bills, and expenses must be recreated manually in FreeAgent. |
| Stock & Inventory | medium | Weighted-average valued stock from QBO must be re-entered as opening quantities at current cost. Historical FIFO recalculation will produce different COGS figures. |
| Attachments & Receipts | medium | No bulk import. Each receipt or document must be manually re-uploaded to the corresponding transaction. |
| Bank Rules & Categorisation | low | Not transferable. FreeAgent uses its own explanation system which must be configured from scratch. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
VAT Opening Balance Lock
Once you file your first VAT return via MTD in FreeAgent, opening VAT balances on codes 817, 818, and 819 are permanently locked and cannot be corrected.
CIS Deduction Continuity
Historical CIS deductions do not transfer via CSV. The initial CIS balance must be entered manually and feeds directly into RTI submissions to HMRC.
Rigid Bank CSV Format
FreeAgent requires exactly three columns (Date, Amount, Description) with no header row, dd/mm/yyyy dates, and signed amounts — most QuickBooks exports need significant reformatting.
Inventory Valuation Mismatch
QuickBooks uses weighted-average costing while FreeAgent uses FIFO. Importing historical stock data produces balance sheet discrepancies from day one.
No Invoice Import Path
There is no native CSV import for historical sales invoices or bills. Third-party tools like AutoEntry or Dext handle individual documents but are not designed for bulk migration.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I use Movemybooks or Dataswitcher to migrate from QuickBooks to FreeAgent?
No. Movemybooks supports FreeAgent as a source platform (migrating data out of FreeAgent) but not as a destination. Dataswitcher is an Intuit-supported tool that migrates data into QuickBooks Online, not out of it. Neither tool can push data into FreeAgent.
How do I import bank transactions into FreeAgent from QuickBooks?
Export your bank transactions from QuickBooks as a CSV, then reformat to FreeAgent's strict 3-column format: Date (dd/mm/yyyy), Amount (negative for outgoings), and Description. No header row. Upload via Banking > Upload a bank statement.
What happens to my VAT history when I switch from QuickBooks to FreeAgent?
VAT history doesn't transfer. You enter opening VAT balances manually using FreeAgent's nominal codes (817, 818, 819). Once your first VAT return is filed via Making Tax Digital, you cannot edit the opening VAT figures — corrections must go into the next open period.
Does FreeAgent support CIS for sole trader subcontractors?
Yes. FreeAgent supports CIS for sole trader and limited company account types. You set it up under Settings > Construction Industry Scheme and enter your initial CIS deduction balance. FreeAgent does not support filing the monthly CIS300 return — you must file that via HMRC's online service.
When is the best time to migrate from QuickBooks to FreeAgent?
At the start of a new VAT quarter and ideally at your financial year-end. This avoids the complexity of mid-quarter VAT splits and gives you a clean trial balance for opening balance entry.