How to migrate from Xero to Sage Intacct
To migrate a client from Xero to Sage Intacct with superglue's AI agent, connect the client's Xero organisation, and give superglue access to the client's Sage Intacct account. superglue assesses the data in minutes, plans every phase, recommends an answer to each decision, and runs a trial load that reconciles to the cent before cutover. You review, decide and sign off with the client.
What are the steps to migrate from Xero to Sage Intacct?
Migrating from Xero to Sage Intacct takes six steps: connect both systems, assess the data, plan every phase, decide the mapping, run a trial load and cut over. Each load repeats exactly what you tested, and every write waits for your approval.
- 01
Connect Xero and Sage Intacct
Connect the client's Xero organisation with one sign-in. superglue reads it through the Xero API and writes nothing. The client then gives superglue access to Sage Intacct.
- 02
Assess the Xero data
In minutes, superglue counts every record, finds the open items and lists the data issues with examples. You know the size of the migration before you quote it.
- 03
Plan every phase
superglue drafts the plan from discovery to cutover, with tasks, owners and the Xero specifics already in it.
- 04
Decide the mapping
superglue brings each decision below with a recommendation from the client's own data. You confirm or change each answer, and the client signs the mapping.
- 05
Run the trial load
superglue loads a Sage Intacct sandbox or implementation company and compares it with Xero: the trial balance per period, the open receivables and payables per customer and vendor, and the inventory value. superglue explains every difference before cutover.
- 06
Cut over
At cutover, superglue loads the final data with the same steps as the trial load, and you sign the reconciliation with the client.
How do you get the data out of Xero?
- Have a user with the Adviser or Standard role sign in once. superglue reads the whole organisation through the API and writes nothing.
- Xero allows each app 5,000 API calls a day for each connected organisation, so superglue spreads a large history read over several days. Start the assessment early.
- The Xero Accounting API does not return unreconciled bank statement lines. Have the client reconcile the bank accounts up to cutover, or export the statement lines.
What needs to be configured in Sage Intacct?
The client authorizes the superglue sender ID in Sage Intacct and adds a user for superglue. superglue configures Sage Intacct and loads the data through that access, in a Sage Intacct sandbox or implementation company first, in this order:
- 01
Multi-entity, the base currencies and the first fiscal month. Base currencies and the first fiscal month can change only before transactions exist.
- 02
The configuration of each module, such as General Ledger, Accounts Payable and Accounts Receivable, and the names of terms and dimensions.
- 03
Entities, locations, departments and the other dimensions.
- 04
The chart of accounts and the journals.
- 05
Customers, vendors and items, then the opening balances and the open items.
Access setup for the client: Sage Intacct configuration guide
What moves from Xero to Sage Intacct?
| In Xero | In Sage Intacct |
|---|---|
| Chart of accounts | GL accounts |
| Tracking categories | Dimensions such as departments, locations and classes |
| Contacts you sell to | Customers |
| Projects | Projects |
| Contacts you buy from | Vendors |
| Items | Items |
| Bank accounts | Checking and credit card accounts |
Open items
Open invoices and credit notes, unallocated overpayments and prepayments, open bills, and open quotes and purchase orders.
Open items load as AR invoices and AP bills with their original numbers, dates and due dates, so the aging in Sage Intacct matches on day one.
History
superglue reads every transaction through the Xero API, and plans a large history read around Xero's daily API limit.
History loads as summary journal entries per month, account and dimension.
Which decisions do you make when you migrate from Xero to Sage Intacct?
- 01
Where do Xero tracking categories go?
Xero allows two active tracking categories. Sage Intacct has departments, locations, classes and user-defined dimensions.
superglue separates the meanings in each tracking category and proposes one dimension for each meaning.
- 02
How do Xero contacts become customers and vendors?
Sage Intacct keeps customers and vendors as separate records.
superglue creates a customer, a vendor or both from the transactions on each contact, with the same name.
- 03
Which companies become entities, and which become locations?
In Sage Intacct, an entity has its own books, tax and bank accounts. A location only adds a reporting value.
superglue recommends one entity for each legal company in Xero, and locations for the sites inside a company.
- 04
Which records are shared across entities?
Customers, vendors and items can live at the top level and be shared, or belong to one entity.
superglue recommends shared customers and vendors, so each company appears once and intercompany reporting stays clean.
- 05
How much history moves?
Most clients need the open items plus one to two years of monthly balances in Sage Intacct, and older years as yearly balances. The client keeps the older detail in an archive.
superglue recommends two years of monthly balances per account, and full transaction detail only where the client needs to look into single transactions.
What are the common challenges when you migrate from Xero to Sage Intacct?
One contact can be a customer and a supplier
Xero keeps customers and suppliers in one contact list. superglue sorts each contact by its transactions, and keeps one name for a company that is both.
Two tracking categories carry too much
Xero allows two active tracking categories, so clients pack several meanings into one list, such as region and product line. superglue separates the meanings before the mapping starts.
Conversion balances start the history
Many Xero organisations started from conversion balances, so the earliest period is a summary. superglue reports the conversion date and the first period with full detail.
Overpayments and prepayments stay open until allocated
An overpayment or prepayment that was never allocated is an open item. superglue moves each unallocated amount as an open credit, so the aged balances match.
Plan module configuration as its own workstream
In Sage Intacct, the settings of General Ledger, Accounts Payable and the other modules cannot be imported like data. Unless the partner starts from a template company, they are set by hand, screen by screen. superglue sets them and checks every value, so the configuration is ready when the data is.
Agree user-defined dimensions with the person who reports on them
A user-defined dimension stays in Sage Intacct once it holds data. Add only the ones the client will report on, and get each one agreed before the first load.
superglue also runs the rest of the Sage Intacct project. See the Sage Intacct implementation
Frequently asked questions
Which data moves from Xero to Sage Intacct?
The chart of accounts, customers, vendors and items, the open items, and as much history as the client needs. The mapping table on this page shows where each record lands in Sage Intacct.
Does superglue write to Sage Intacct without my approval?
No. superglue only reads Xero. Before any write to Sage Intacct, it shows the target, the connection and a transformed sample, and waits for your approval.
How do I know the migration is complete?
superglue reconciles the trial load and the final load against Xero: the trial balance per period, the open receivables and payables per customer and vendor, and the inventory value. You get a reconciliation report to sign with the client.
What happens when I start this migration?
You sign up and connect the client's systems. If you want to see a full migration run first, superglue can set up Pinecrest Supply, a sample client.
Start your Xero to Sage Intacct migration
Sign up and connect the client's systems, or let superglue set up Pinecrest Supply, a sample client, to see a full migration run first.