Why migrations aren’t copy-paste: how accounting data differs across software

People expect moving between accounting systems to be like moving a spreadsheet — copy the rows, paste them somewhere new. It never is, and the reason is that no two systems store the same information the same way. The concepts are universal; the data models are not. Understanding where they diverge is the difference between a clean migration and a broken file.

The same idea, different structures

Take “a customer.” One system stores customers and vendors as separate lists; AccountEdge keeps customers, vendors and other contacts together as unified “cards” you have to split apart. A migration has to reshape the data, not just move it.

Account types don’t line up

Every system has account types, but the exact set and their behaviour differ. Map an account to the wrong destination type and it passes the import but quietly distorts the balance sheet — invisible until a report looks wrong.

Fields that exist here but not there

One system tracks a piece of data as a dedicated field; the destination has no home for it. Jobs, classes, departments, segments, tax codes — these force real decisions. A Sage segmented account number has no direct QuickBooks equivalent; part becomes an account and part becomes a class.

Tax is its own small system

Sales tax isn’t a single number — it’s items, agencies and liability accounts wired together, and every product wires them differently. This is why tax so often lands wrong after a migration.

The same invoice, three shapes

An invoice in Sage, QuickBooks and Zoho carries the same meaning but different required fields, line-item rules, and links to master data. A converter’s real job isn’t copying — it’s translating each system’s shape into the destination’s, and validating that the translation holds.