Moving accounting records into Xero should give your business clearer reporting and easier access to financial information. However, a migration can fail when data is imported incorrectly, important records are missing, or balances do not match the previous system.
A failed Xero migration does not always mean your financial data has been permanently lost. In many cases, the original data still exists but has been imported, mapped, or recorded incorrectly.
The most important step is to stop making further changes until you understand what went wrong. Random corrections can make the problem harder to trace.
This guide explains how to identify migration errors, protect your records, correct the problem, and confirm that your Xero account is reliable.
Worried about a failed Xero migration? Contact Cloud Accounting today to protect your financial data and restore accurate records before the errors grow.
What Is a Failed Xero Migration?
A failed Xero migration happens when accounting data does not arrive in Xero accurately or completely.
The import may have finished without displaying an error, but the financial position could still be wrong. For example, the profit and loss report may look reasonable while bank balances, unpaid invoices, or VAT figures remain incorrect.
Common signs include:
- Opening balances do not agree with the previous system
- Customer or supplier balances are incorrect
- Bank transactions have been duplicated
- Invoices or bills are missing
- Payments are not linked to the correct documents
- Account codes have been mapped incorrectly
- VAT rates have changed during the move
- Historical reports do not match
- Foreign currency balances are wrong
- Tracking information has disappeared
- Transactions appear in the wrong financial period
- Reports contain unexpected conversion balances
A successful migration is not confirmed simply because the files were accepted. The figures in Xero must also agree with the source records.
First, Stop Entering New Transactions
If you discover a failed migration, pause further bookkeeping in the affected Xero organisation.
Continuing to raise invoices, reconcile bank transactions, or submit VAT returns may mix new activity with incorrect migrated data. This makes it harder to separate the original migration problem from later entries.
Ask everyone with access to Xero to pause their work while the issue is reviewed. You may also need to disconnect bank feeds or connected apps temporarily if they are adding new records.
Record the date and time when the problem was discovered. You should also note which users, apps, or migration tools have changed the organisation since the import began.
The aim is to preserve the current position while you investigate.
Protect the Original Financial Data
Never rely on the failed Xero organisation as the only copy of your accounting records.
Before correcting anything, secure the original information from the previous accounting system. Depending on the software, this may include a complete backup, database file, or a set of detailed exports.
Keep copies of:
- Trial balance
- Balance sheet
- Profit and loss report
- General ledger
- Chart of accounts
- Customer list
- Supplier list
- Sales invoices and credit notes
- Purchase bills and supplier credits
- Customer and supplier activity
- Bank account transactions
- Bank reconciliation reports
- VAT returns and VAT reports
- Fixed asset register
- Payroll records
- Inventory records
- Foreign currency balances
- Tracking, department, or project reports
- Supporting documents and attachments
Store these records securely and avoid changing the original files. Create working copies for review and correction.
You should also export the current information from Xero before starting the repair. This provides evidence of what was imported and helps you compare the failed result with the source data.
Identify Exactly What Went Wrong
Do not delete and repeat the entire migration before finding the cause. If you use the same files and mapping rules, you may simply create the same errors again.
Start by dividing the migration into separate areas:
- Organisation and financial settings
- Chart of accounts
- Conversion balances
- Contacts
- Sales invoices
- Purchase bills
- Credit notes
- Payments
- Bank accounts and statement lines
- Manual journals
- Fixed assets
- VAT information
- Foreign currencies
- Tracking categories
- Connected apps
Check each area against the source system.
A structured review helps you determine whether the problem is limited to one import or affects the whole Xero organisation.
Check the Conversion Date
The conversion date controls when the business begins using Xero as its main accounting system.
If the date is wrong, opening balances may fall into the wrong period. Transactions can also overlap with imported history, creating duplicated income, expenses, assets, or liabilities.
Check that the conversion date agrees with:
- The final period completed in the old system
- The opening date used in Xero
- The date of the conversion balances
- The first bank statement line imported into Xero
- The first day of live bookkeeping in Xero
For example, if the final completed month in the old system ends on 31 March, Xero would normally begin from 1 April. The exact approach depends on the agreed migration scope and the financial records being transferred.
Review the Chart of Accounts
A chart of accounts controls where financial transactions are recorded. Incorrect mapping can make the whole migration appear unreliable even when the transaction values are present.
Check for:
- Duplicate account codes
- Missing accounts
- Incorrect account types
- Revenue recorded as liabilities
- Expenses recorded as assets
- Bank accounts created as ordinary ledger accounts
- Tax rates assigned to the wrong accounts
- Old accounts mapped into unsuitable Xero categories
- Multiple source accounts merged without approval
- System accounts used incorrectly
Some Xero accounts are locked or reserved for specific purposes, so the old structure may not transfer exactly as it was.
Reconcile the Conversion Balances
Conversion balances represent the financial position brought into Xero at the chosen conversion date.
Start with the trial balance from the previous system and compare every account with Xero.
The total debit balance must equal the total credit balance. However, a balanced trial balance does not automatically mean the figures are correct. Two equally incorrect entries can still balance.
Pay close attention to:
- Bank balances
- Accounts receivable
- Accounts payable
- VAT control accounts
- Payroll liabilities
- Loans
- Director loan accounts
- Fixed assets
- Accumulated depreciation
- Inventory
- Retained earnings
- Foreign currency balances
The receivables balance should agree with the total unpaid customer invoices. The payables balance should agree with the total unpaid supplier bills.
If these figures do not match, investigate the difference before entering a balancing adjustment. A suspense entry may hide the problem without fixing it.
Find Missing or Duplicate Transactions
Duplicates often appear when the same historical period is included in more than one import.
For example, sales invoices may have been included in the opening balances and then imported again as individual transactions. Bank statement lines may also be duplicated when both a manual statement file and a live bank feed cover the same dates.
Compare transaction counts and values by month.
Look for:
- Duplicate invoice numbers
- Repeated bank references
- Identical dates and values
- Credit notes imported more than once
- Payments appearing without invoices
- Invoices included in both history and opening balances
- Journals duplicated during separate import attempts
- Bank transfers recorded as income or expenses
Confirm that a line is genuinely duplicated before deleting it. Two transactions with the same value and date may still be legitimate.
Match Payments to Invoices and Bills
A migration may bring across invoices and payments as separate records without connecting them.
This can cause paid invoices to appear overdue and may create an incorrect accounts receivable or accounts payable balance.
Review:
- Customer payments
- Supplier payments
- Part payments
- Overpayments
- Prepayments
- Credit note allocations
- Refunds
- Payments made in foreign currencies
Compare the aged receivables and aged payables reports in Xero with reports from the old system.
Do not create new payments simply to close invoices unless you have confirmed that the original payments are missing. Otherwise, you may duplicate cash movement and distort the bank balance.
Review Bank Accounts and Reconciliation
Bank errors are among the most visible signs of a failed Xero migration.
The balance shown in Xero can be wrong because of:
- Missing statement lines
- Duplicate statement imports
- Transactions imported into the wrong bank account
- Incorrect opening balances
- Reconciliations completed against the wrong entries
- Transfers recorded incorrectly
- Bank feeds starting too early
- Payments imported without matching statement lines
Compare three figures for each account:
- The bank statement balance
- The source accounting system balance
- The Xero balance
Check the full date range rather than reviewing only the current balance. An old error may be hidden by a later transaction of the same value.
If bank statement lines were imported into the wrong account, review the available correction options before deleting or reimporting anything.
Check VAT Treatment Carefully
A failed Xero migration can affect VAT reports even when the net transaction values look correct.
Review:
- VAT registration details
- VAT rates used on imported transactions
- VAT exclusive and inclusive amounts
- Previous VAT return periods
- Unfiled VAT transactions
- VAT control account balances
- Credit notes and refunds
- Reverse charge transactions
- Import VAT
- Flat Rate Scheme treatment, where relevant
Compare the final VAT return from the old system with the opening VAT position in Xero.
Do not submit a VAT return from the new organisation until the migrated VAT records have been checked. Incorrect tax mapping can affect both the return and the underlying accounting reports.
Where previous returns have already been filed with HMRC, take particular care before editing transactions included in those periods.
Review Foreign Currency Data
Foreign currency migrations require more than transferring the original invoice value.
You may also need to preserve:
- Original currency
- Exchange rate
- Base currency value
- Unpaid foreign currency amount
- Realised currency gains or losses
- Bank account currency
- Conversion date exchange rate
If an invoice is imported using the wrong currency or exchange rate, its outstanding value may not agree with the previous system.
Compare foreign currency receivables, payables, and bank accounts separately. Do not rely only on the total balance expressed in the base currency.
Decide Whether to Repair or Start Again
Not every failed Xero migration should be corrected transaction by transaction.
A repair may be suitable when:
- The problem affects a limited number of records
- The correct source data is available
- Errors can be identified clearly
- New bookkeeping has already started in Xero
- The organisation contains valid work that should be preserved
Starting again in a new Xero organisation may be safer when:
- Most imported data is unreliable
- The conversion date is fundamentally wrong
- There are large numbers of duplicates
- Account mapping is unsuitable
- The same data has been imported several times
- There is little or no valid work to preserve
- Correcting the organisation would cost more than rebuilding it
This decision should be based on evidence. A rushed restart can lose valid work, while a complicated repair can leave hidden errors behind.
Create a Controlled Recovery Plan
Once the problem has been identified, document the repair steps before making changes.
Your plan should state:
- Which data is correct
- Which data is incorrect
- Which records will be removed
- Which records will be corrected
- Which records will be reimported
- Who will approve the changes
- What reports will be used for testing
- When normal bookkeeping can restart
Work through the migration in a controlled order:
- Confirm organisation settings
- Correct the chart of accounts
- Confirm the conversion date
- Repair conversion balances
- Correct contacts
- Import or repair invoices and bills
- Match payments and credits
- Correct bank statement activity
- Review VAT
- Review foreign currency and fixed assets
- Complete final testing
Keep a written record of every material change.
Test the Repaired Xero Organisation
The repair is not complete until the numbers have been tested.
Compare Xero with the old accounting system at the conversion date and at selected later dates.
At a minimum, review:
- Trial balance
- Balance sheet
- Profit and loss report
- Aged receivables
- Aged payables
- Bank balances
- VAT control account
- Retained earnings
- Fixed asset balances
- Foreign currency balances
- Transaction counts by period
Investigate every unexplained difference, even if it appears small. A minor balance may point to a larger mapping or timing problem.
Where possible, ask someone who did not perform the original import to review the results. A fresh pair of eyes is often useful in migration work.
Set Lock Dates After Approval
Once the historical data has been checked and approved, consider setting lock dates in Xero.
Lock dates help prevent users from changing transactions in completed periods. Different access levels may apply depending on the type of lock date used.
Before locking a period, confirm that:
- Opening balances are correct
- Historical bank accounts reconcile
- VAT periods have been reviewed
- Customer and supplier balances agree
- Final reports have been saved
- Your accountant has approved the position
A lock date cannot correct bad data, but it can help protect verified records from later changes.
How to Prevent Another Failed Xero Migration
Most migration problems can be reduced through careful preparation and testing.
Before the next import:
- Agree the migration scope in writing
- Decide how much financial history is needed
- Choose a clear conversion date
- Clean the source data
- Reconcile all bank accounts
- Review customer and supplier balances
- Confirm VAT records
- Remove or explain duplicate accounts
- Document all account mapping
- Test a sample before importing everything
- Keep secure copies of all source reports
- Prevent overlapping bank feed dates
- Complete a full post migration review
- Obtain approval before going live
Do not judge success by the number of records imported. The real test is whether the business can trust the resulting reports.
When Should You Seek Professional Help?
Consider specialist support when the failed migration involves:
- Several years of accounting history
- Large transaction volumes
- Multiple bank accounts
- VAT errors
- Foreign currencies
- Inventory
- Payroll balances
- Fixed assets
- More than one legal entity
- Complex account mapping
- Missing source records
- Several unsuccessful import attempts
- Previously filed financial periods
A migration specialist should review both the source system and the Xero organisation. Looking only at Xero may show the symptoms but not the cause.
Fix Your Failed Xero Migration with Cloud Accounting
A failed Xero migration can leave you with missing records, duplicate transactions, incorrect balances, and reports you cannot trust. These problems should be corrected before the new system becomes the main source of financial information.
Cloud Accounting can review the original records, identify migration errors, repair or rebuild the Xero organisation, and test the final balances before handover.
Whether your data came from Sage, QuickBooks, FreeAgent, KashFlow, an ERP system, or another accounting platform, we can help you establish a reliable position in Xero.
Do not let incorrect migration data become next year’s accounting problem. Contact Cloud Accounting today for a professional review of your failed Xero migration.
