Xero Data Restructuring During Migration
A migration does not have to copy every legacy code and workaround into Xero. With an agreed mapping, historical data can be preserved while the destination structure is simplified for future reporting.
Restructuring is different from “fixing” the accounts
Our starting point is to preserve the accounting result, not silently rewrite history. Restructuring changes how agreed source data is represented in Xero: for example, several legacy nominal codes may map to one new account, or old departments may be reorganised into an agreed tracking structure.
If the source contains an accounting discrepancy, that is raised separately and the treatment is agreed with the client or accountant.
Chart of Accounts restructuring
Legacy systems can accumulate hundreds of codes, duplicates or entity-specific conventions. During migration, codes can be mapped into a cleaner Xero Chart of Accounts where the future reporting structure has been agreed.
For groups, this can also be an opportunity to standardise the Chart of Accounts across entities rather than perpetuating different structures indefinitely.
Contacts, dimensions and analysis
Customer and supplier records can be rationalised where matching rules are clear. Departments, cost centres and other source dimensions can be assessed for Xero tracking rather than copied mechanically.
The important part is to design the destination first. Historical transactions are then transformed against that agreed mapping so reporting remains explainable.
Keep a clear mapping trail
Restructuring makes documentation more important, not less. We retain mapping schedules and reconciliation evidence so the finance team can understand how the source structure became the Xero structure.
That is what allows a cleaner future design without losing confidence in the historical numbers.
What restructuring can look like during migration.
The objective is not cosmetic clean-up. Each change needs an agreed rule and a clear relationship between the legacy structure and the future Xero organisation.
| Source structure | Migration decision | Possible Xero outcome |
|---|---|---|
| Large or duplicated Chart of Accounts | Map or consolidate where agreed | Cleaner reporting structure |
| Departments or cost centres | Decide what analysis should continue | Xero Tracking structure |
| Duplicate or inconsistent contacts | Agree consolidation and naming rules | Cleaner contact records |
| Unallocated historical items | Review treatment before import | More meaningful aged reporting |
| Different coding across a group | Standardise where appropriate | More consistent group reporting |
Explore related migration expertise
Jump directly to the related service, guide or specialist topic.
Group migrations
Standardisation and restructuring across multiple entities.
Explore →CoreHistorical data migration
Preserve history while changing the future-state structure.
Explore →GuideMigration checklist
Prepare the source data and decisions before migration.
Explore →ComplexBespoke migrations
For mapping and transformation requirements outside standard routes.
Explore →Common questions.
Can you change the Chart of Accounts during migration?
Yes. Source codes can be mapped or consolidated into an agreed Xero Chart of Accounts while retaining a documented mapping trail.
Can we standardise multiple companies?
Yes. Group migrations are often a good opportunity to agree a common account and reporting structure.
Do you clean up contacts?
Contact restructuring can be included where matching and naming rules can be agreed safely.
Does restructuring change historical financial results?
It should not silently change the accounting result. Structural mapping and accounting corrections are treated as separate decisions.
Can departments and cost centres become tracking categories?
Often yes. We review the source analysis fields and agree how they should translate into Xero tracking within Xero's current capabilities.
Tell us about the source system, history and future Xero structure.
