Know What Your AI ERP Will Actually Migrate Before You Sign

A two-page checklist for controllers and CFOs: 10 questions to ask in the demo, the answer that should reassure you, and the one that should stop you from signing.

What's Inside the Checklist

Ten questions that follow your data from the demo to your first close: track record, de-duplication, chart of accounts changes, summary versus transaction-level loads, open AR and AP, rev rec history, exceptions, and who signs off on the result. Each question explains why it matters and what a strong answer and a red flag sound like. It fits on two pages, so you can print it and take notes while the vendor answers.

A Sample Question: Who owns de-duplicating our customer, vendor, and item lists?

Safe answer: The AI surfaces candidates, but a person who knows the difference between "Acme Corp" and "Acme Corp West" makes the final call.

Red flag: "The AI handles it," with no human review step or exception report mentioned.

  • Who it's for: Controllers and CFOs moving off QuickBooks or Sage who have an AI-native ERP on the shortlist and a demo on the calendar.
  • Why it matters now: The demo is the last point where you can make the vendor show its work. After you sign, every gap in the migration becomes your team's cleanup project.

What You'll Know Before You Sign

  • Whether "fast, AI-powered migration" covers your open invoices and transaction history, or just your customer list and a trial balance
  • Which vendor answers you can trust: "30+ migrations from QuickBooks Online" counts, "we've done a lot of these" doesn't
  • What your reporting loses if transactions arrive as summary journal entries, before your board deck is the place you find out
  • Who answers the phone six months after go-live, when your auditor asks how the data got there

Earlier this year, a multi-entity SaaS company told us its AI ERP vendor would connect to QuickBooks and pull the data over itself. Then their implementation partner flagged that full transaction-level history was the hard part. They needed five years of it for lender and quality-of-earnings reviews.

FAQs

The demo shows the software, not your data inside it. A vendor's "fast" migration might cover master records, historical transactions, and open items, or only the first of those. Your auditors will also want the migration process documented, not just the totals tied out.

It's a fair question. We migrate data into NetSuite for a living, and for some companies, an AI-native ERP is the right call. Every question here applies just as much to NetSuite as it does to us. A vendor with a real migration process will answer all ten without difficulty.

Controllers and CFOs evaluating an AI-native ERP. It's most useful if you run multiple entities, recognize subscription revenue, or need years of history for lenders, investors, or a future quality-of-earnings review.

Mostly safe answers is a good sign. Three or more red flags is worth slowing down for before you sign, especially on summary versus individual transactions, exception handling, and who validates the data.

Paul Giese, founder of OptimalData Consulting. Our team has led 100+ NetSuite data migrations from QuickBooks and Sage, and Paul has spoken at SuiteWorld. The questions come from what we've seen go wrong once real data starts moving.

Go Deeper

Ready to Talk Through Your Migration?

Let's Talk