Sage Intacct to Xero Migration: How a 5-Day Financial Data Migration Was Completed

Moving financial data from Sage Intacct to Xero is not a simple export-import job. Intacct is a multi-entity, multi-dimensional ERP. Xero is a streamlined accounting platform built for smaller organizations. The structural gap between them is the real challenge — not the timeline.

This post documents what actually happens during this migration path: what transfers cleanly, what gets flattened, what breaks, and how to validate the result.

Why Sage Intacct to Xero Migrations Are Structurally Complex

Sage Intacct supports true multi-entity consolidation, user-defined dimensions (locations, departments, classes, projects), and deep transactional history across modules like GL, AP, AR, and fixed assets. Xero does not have direct equivalents for most of these structures.

This means the migration is not just a data transfer — it is a data transformation. Key structural incompatibilities include:

How the Sage Intacct API Extraction Works

Sage Intacct does not offer a bulk data export button. Extracting data at scale requires API access, which means setting up authentication and understanding the available endpoints.

OAuth App Setup

To connect to the Sage Intacct Web Services API, the account owner must generate an OAuth application within their Intacct tenant. The steps:

1. Navigate to Company → Web Services Authorizations in the Sage Intacct admin panel.
2. Create a new Web Services sender ID (or use an existing one if your subscription includes API access).
3. Generate API credentials — a sender ID and sender password — that authorize external applications to make API calls.
4. Provide the company ID, user ID, and user password for the specific Intacct entity being migrated.

Once credentials are in place, data extraction happens through Intacct's XML-based API. The key objects to extract typically include:

• GLENTRY / GLBATCH — General ledger transactions
• APBILL / APPAYMENT — Accounts payable bills and payments
• ARINVOICE / ARPAYMENT — Accounts receivable invoices and payments
• GLACCOUNT — Chart of accounts
• CONTACT — Customer and vendor records
• DEPARTMENT / LOCATION / CLASS — Dimensional data
• SODOCUMENT — Sales order documents (if applicable)

The API supports pagination through readMore tokens, and rate limits depend on your Intacct subscription tier. For large datasets, extraction runs are typically batched by module and date range.

Importing Into Xero

Xero accepts data through two primary channels:

• Xero API (OAuth 2.0) — Best for programmatic imports of invoices, bills, contacts, bank transactions, and manual journals. Rate-limited to 60 calls per minute per connection.
• CSV import — Available for contacts, chart of accounts, invoices, and bank statement lines. Useful for smaller datasets or one-time loads, but limited in what it can carry (no attachments, no custom field mapping).

For migrations involving thousands of records, the API path is the only viable option. CSV imports hit formatting and volume limits quickly, and they cannot handle attachment linking or transaction-level metadata.

Fiscal Year Cutoff Strategy

Most Intacct-to-Xero migrations do not transfer the full transaction history record-by-record. Instead, the standard approach is:

1. Set a cutoff date — typically the start of the current fiscal year.
2. Import opening balances as a single journal entry in Xero as of that cutoff date.
3. Import detailed transactions only for the period after the cutoff.
4. Archive historical Intacct data separately (PDF reports, data exports) for audit and compliance purposes.

This approach avoids bloating Xero with years of dimensionally-rich data it cannot properly report on.

A 5-Day Migration Timeline: What Each Day Looks Like

We completed this migration path for a client in five business days. Here is the general structure of how an aggressive timeline breaks down:

Post-Migration Validation

Data integrity confirmation is the step most migration providers skip or hand-wave. Here is what a proper validation looks like for this migration path:

1. Trial balance comparison — Pull the trial balance from Intacct as of the cutoff date. Compare it line-by-line against Xero's trial balance for the same date. Every account must match.
2. AR aging reconciliation — Compare the aged receivables report from both systems. Open invoice counts and total amounts must align.
3. AP aging reconciliation — Same process for payables. Outstanding vendor bills must match.
4. Bank account balances — Verify that each bank account balance in Xero matches the corresponding Intacct bank register.
5. Contact count verification — Confirm that the number of active customers and vendors in Xero matches the source. Check for duplicates caused by the customer/vendor merge.
6. Attachment spot-check — Randomly select 20–30 transactions and verify that attachments are present and linked to the correct record in Xero.
7. Tracking category spot-check — For transactions that carried dimensional data in Intacct, verify that the mapped tracking categories appear correctly in Xero.

If any discrepancy is found, trace it back to the transformation layer — not the source or destination. The mapping logic is where errors live.

Common Failure Modes in This Migration Path

• Dimension loss without documentation. The client agrees to flatten dimensions during migration, then six months later their CFO asks why departmental reporting is gone. Document every mapping decision in writing before migration begins.
• Opening balance mismatches. If the cutoff journal does not account for retained earnings, the Xero balance sheet will not balance. Always include a retained earnings line in the opening balance journal.
• Duplicate contacts. Intacct allows a single entity to be both a customer and a vendor. Xero uses one contact record. If not de-duplicated during transformation, the contact list doubles.
• Attachment orphaning. Attachments extract from Intacct as files, but linking them to the correct Xero transaction requires matching on invoice/bill numbers. If numbering schemes change during migration, attachments land unlinked in Xero Files.
• Rate limit throttling on Xero's API. At 60 calls per minute, importing 10,000+ records takes careful batching. Naive implementations hit 429 errors and stall.