Most businesses migrate accounting platforms once. Half lose invoice history in the process. The gap isn't always obvious—a missing custom field here, a broken tax code link there—until your auditor asks why the aging report doesn't match your trial balance. By then, you've already written off time reconciling phantom data. QuickBooks Online exports cleanly on the surface. Open the file. It has rows. It has columns. Then you import into Xero or Wave or Orin , and twelve things stop matching. This audit maps those nine breaks—where they happen, why, and which platforms catch them automatically versus which leave you with manual work. The nine invoice data orphans during QuickBooks export Every export break falls into one of these categories. Know them before you touch the export button. 1. Custom fields and line-item attributes QuickBooks lets you attach custom fields to invoices and line items. A manufacturer tags invoices with job codes. A services firm links line items to cost centers. When you export, QuickBooks includes those fields in the CSV, but most accounting platforms don't have a standard import path for them. They arrive as orphaned columns. You see the data in the export. It vanishes on import. What happens: Custom fields exist in QuickBooks but not in your new platform. You lose the ability to filter by them, report against them, or link them to budget tracking. 2. Invoice line-item tax codes and tax settings per line QuickBooks lets you assign different tax codes to different line items within a single invoice. One line is taxable, another is exempt. When exported, those line-level tax settings often collapse into a single invoice-level tax treatment. Xero preserves them better than Wave. Neither matches QuickBooks exactly. What happens: Invoices import with wrong total tax amounts. Your aged receivables report shows the right invoice total but wrong tax breakdown. Reconciliation fails silently for months. 3. Customer links and multicompany transaction references If you manage multiple QuickBooks companies (common for franchise owners or holding companies), invoices reference customers that may not exist in the target company or may exist with different IDs. QuickBooks uses internal customer record IDs. Export files use customer names. If your customer list has duplicates or variations in spelling, the import logic guesses wrong. What happens: Invoices import under a wrong customer, or create duplicate customer records. Your revenue reports split revenue across two customer entries for the same actual company. 4. Payment application history and unapplied credits QuickBooks tracks which payments were applied to which invoices, and which invoices carry unapplied credits. That relationship data is complex. Most export formats flatten it into invoice status (paid, unpaid, partial). You lose the detail of how a partial payment was allocated, which matters for disputes and reconciliation. What happens: An invoice shows as "paid" in the new platform but your customer insists they applied a credit to it. Your aging report is functionally correct but operationally useless for collections. 5. Aging buckets and payment aging calculations QuickBooks calculates aging (30, 60, 90+ days) based on invoice date and current date at export time. That snapshot is static. If you export on June 15, all invoices are bucketed as of June 15. Import that same data on July 15, and it's already stale. Most platforms recalculate aging on import, which is correct—but if you have a reporting gap between export and import, you'll see aging shifts that don't match your QuickBooks records. What happens: Your June aging report from QuickBooks doesn't reconcile to the July aging report in the new platform, even though logically it should. Reconcilers assume data corruption. 6. Memo and description fields across three levels QuickBooks invoices have memos at three levels: invoice-level memo, line-item description, and line-item memo. Export typically includes all three as separate columns. Import logic varies: some platforms jam them together, some drop the line-item memo, some preserve all three but in a different field order. Your free-text data arrives but reorganized, making search and audit trails harder. What happens: A note you added to an invoice line (e.g., "Client requested net-60 terms") ends up in a different field, invisible to your new platform's invoice view. You can retrieve it from the data, but not from the UI. 7. Tags, classes, and cost allocation codes QuickBooks "class" feature segments transactions by department, project, or cost center. Some firms use it as a full P&L split. Export includes class data, but the receiving platform may call it "tags" or "dimensions" or "cost centers" with different hierarchies and limits. Xero supports unlimited dimensions. Wave supports tags but with looser semantics. Mapping is manual. What happens: You export 5,000 invoices with class assignments. Import creates 500 new ta