Migrating from Another Xero Connector

If you already have a Xero connector, its records are linked to Xero in its own way: each Xero contact tied to an Account, each invoice tied to an Opportunity. The Migrate to TCC tool preserves those links so your history stays connected rather than starting over.

How it works

Your old connector and TwoCanConnect both identify Xero records by the same Xero ID. The tool scans your org for wherever the old connector stored those IDs, reads the relationships attached to them, and re-applies the relationships to TwoCanConnect's records by matching on the shared ID. It's an exact match, not guesswork, and it works with any connector that stored the ID, including an in-house build.

The scan compares against Xero records TwoCanConnect has already synced, so run the historical sync first, then the migration tool.

Before you scan: two settings

The Detect step warns about two settings that leave a migration incomplete or messy. Fix both before any sync runs.

• Contact Types to Sync → Both. If only customers sync, supplier-only contacts never reach Salesforce and their old links can only land in Needs review. Set it under Sync Settings.
• Product Sync Mode → Stage. If your org has products that aren't linked to Xero and the mode is auto-create, the historical sync creates duplicate products instead of matching the ones you have. Duplicates are painful to unpick because invoices raised afterwards reference the wrong product. Set it to Stage, sync, then match products in the Matching Tool.

The order

1. Finish setup, with the two settings above in place.
2. Run the historical sync for everything.
3. Open Migrate to TCC, pick the Xero organisation, Scan my org.
4. Review the Map step and Stage these links.
5. Apply to synced records. Links are filled onto the records the sync created, only where the field is still blank.
6. Anything in Needs review hands off to the Matching Tool with Finish N in the Matching Tool.

The four steps in the tool

1. Detect — pick the Xero organisation and Scan my org. The banner names the connector if it recognises one, but discovery works by value, so an in-house build is found the same way. Scanning changes nothing.
2. Map — each discovered group shows the field the IDs live in and a coverage percentage (12 of 12 sampled Xero IDs matched), then the links it can preserve. A missing-field row means the old connector linked to something TwoCanConnect has no field for, such as Invoice → Case. Create field adds the lookup for you, or create it yourself and click Verify, then re-scan. Click Stage these links.
3. Apply — Apply to synced records. It's safe to re-run: it only fills blank links. (Pre-seed before sync is for the rare case where you scanned before the historical sync ran; with the sync done, use Apply.)
4. Review — Linked rows matched exactly by Xero ID. Needs review rows had no exact match, usually because the old connector didn't store an ID for them. Finish N in the Matching Tool resolves those with fuzzy matching.

Cutting over

1. Check a sample of older invoices open correctly against Xero.
2. Run the matching tool for anything the migration couldn't link.
3. Turn off the old connector's sync before starting TwoCanConnect's ongoing sync. Two connectors syncing the same Xero organisation fight each other and create duplicates.
4. Once you've verified the results, uninstall the old connector.