More guides
Popular blogs
Company
Scoping, reconciliation, and the hard-won lessons behind clean ERP migrations to NetSuite.
Which historical transactions to bring into NetSuite, and which to leave behind. A per-record-type default and the four questions that flip it for your books.
AI can now read QuickBooks and write to NetSuite over MCP. Here is how the plumbing works, what an agent does well, and why it cannot yet finish a migration you would sign off on.
If you're bringing multiple QuickBooks companies into one NetSuite OneWorld account as separate subsidiaries, you'll probably run into this: a vendor or item name NetSuite says already exists, because it checks uniqueness for the whole account, not per subsidiary. Merging looks like the obvious fix. This post walks through why that's worth reconsidering, and what to do instead, by hand or with a migration tool.
Journal entries always post, which makes them a tempting shortcut for migrating customer payments, vendor payments, and deposits. They also leave the invoices and bills they were meant to settle sitting open, and the reports you would check don't show it.
QuickBooks tracks a class and a location. NetSuite tracks department, location, and class. How to decide where each of your values belongs in a QuickBooks-to-NetSuite migration, and what to check before the first push.
A trial balance that ties proves the buckets weigh the same — not that the same transactions are in them. Here's the class of migration errors that leaves every total intact, and what record-level reconciliation catches that aggregate checks can't.
QuickBooks stores one name for a customer. NetSuite stores an auto-numbered Customer ID, a company name with no uniqueness rule, a Company or Individual flag, and first and last name fields QuickBooks never split. Which of those your import lands in decides whether it works.
A trial balance, a customer list and the transactions still open at cutover is a few hundred rows and a couple of afternoons. Spreadsheets are fine for that. This is what breaks when you use them to move everything instead, taken from a real NetSuite import session: values that were never in the file, a column mapped to the wrong field, dates that read as valid, and a job reporting Complete after importing nothing.
Moving from QuickBooks or Xero to NetSuite? Learn what field mapping means, what can go wrong, and how to choose and test your migration approach.
Scoping calls ask people to describe a dataset nobody has counted, and the answers become a fixed fee and a go-live date. The four things that actually size a migration are volume, span, shape and condition, and all four are measurable before you quote.
A full data migration to NetSuite is more than opening balances. Five challenges that show up when customers, vendors, items, and transaction history all have to land intact: account mapping, source transactions, customers and vendors, transaction type, and push order.
