Sample output from the ERP Migration Readiness Assessment prompt in the Sonar AI Prompt Library, run against a NetSuite test account. Every name and number here is test data. Back to the post · The library

ERP Migration Assessment

A data-driven profile of NetSuite account TD3095666, the requirements it implies, candidate replacement platforms, and an honest view of what a migration would involve.
August 8, 2026Assessment date Live instance dataSource (SuiteQL / account APIs) ProductionEnvironment Prepared by Sonar AIIn-instance analysis agent

1Executive Summary

This assessment was built from the instance itself — enabled features, subsidiary structure, transaction volumes by type, and the customization/scripting footprint — rather than from assumptions. Three findings dominate everything else:

🏭 You are a manufacturer-distributor, not a "generic" NetSuite shop

Work orders, assembly builds, ECOs, wave picking, bins, lot/serial tracking, requisition-to-pay, rebates and AR deductions are all in live use. Finance-first ERPs are disqualified on day one.

🔌 The integration surface is the long pole

465 RESTlets and 704 Suitelets mean external systems and custom UIs depend on this account programmatically. Cataloging and re-pointing those — not moving data — is the hardest, longest part of any migration.

🌏 Multi-entity, multi-country is non-negotiable

Six subsidiaries across the US, Canada, and Vietnam with an elimination entity and VAT filing. Any candidate must prove consolidation and VN/CA localization — a common failure point for mid-market ERPs.

Bottom line The strongest-fit candidates are Microsoft Dynamics 365 Business Central and Acumatica, with D365 Finance & SCM or SAP S/4HANA Public Cloud only if you expect substantial growth in international/rebate complexity, and Epicor Kinetic / Infor SyteLine if shop-floor depth becomes the priority. Realistic timeline for this profile: 9–18 months with an implementation partner. Avoid finance-only suites (Sage Intacct, QuickBooks-tier) and low-API platforms entirely.

2Instance Profile — What This Account Actually Is

All figures below were queried live from the account on the assessment date.

6
Subsidiaries (OneWorld)
US HQ, US 1, US 2, US Elimination, Canada, Vietnam
3
Currencies in play
USD, CAD, VND (multi-currency feature itself is off — currencies come from subsidiaries)
~24K
Transactions
Dec 2023 → present (~2.5 years of history)
20
Locations
with 154 bins, wave picking, lot/serial tracking on 130 items
331
Customers
Master data is small — easy to migrate
75
Vendors
P2P is the highest-volume process area
402
Items
incl. 50 assemblies, 130 lot/serial-tracked
183
Employees
216 GL accounts

Subsidiary structure

SubsidiaryCountryRole
HeadquartersUSParent / consolidation top
US 1USOperating entity
US 2USOperating entity
US Elimination SubsidiaryUSElimination entity — intercompany eliminations are in active use
CanadaCAOperating entity (CAD)
VietnamVNOperating entity (VND) — VAT online filing configured

Transaction volumes by process area (all-time)

Purchase Orders
3,894
Item Receipts
3,806
Vendor Bills
3,707
Vendor Payments
3,470
Sales Orders
2,001
Item Fulfillments
1,868
Invoices
1,865
Customer Payments
1,472
Work Orders
252
Journal Entries
164
WO Completions
145
WO Issues
132
Assembly Builds
127
Inventory Adjustments
94

Long tail also in use: inventory revaluations (78), bin transfers (62), credit memos (49), pick waves (42), inventory transfers (26), vendor return auths (15), customer RMAs (15), blanket POs, vendor prepayments, transfer orders, unbuilds, expense reports, commissions, ownership transfers. Blue = procure-to-pay, green = order-to-cash, orange = manufacturing/inventory. P2P is your highest-volume pipeline; the manufacturing loop (WO → Issue → Completion → Build → Close) is fully exercised.

Customization & automation footprint

8,060
Custom fields
Large share bundle-installed (FAM, WMS, rebates, deductions) — needs triage
655
Custom record types
~88 clearly bundle-namespaced; ~567 need review for live business data
2,275
Script records
Across 18 script types — see breakdown below
31
Workflows
Plus 19 workflow action scripts
Suitelets (custom UIs)
704
RESTlets (custom APIs)
465
User Event scripts
384
Client scripts
226
Map/Reduce (batch jobs)
206
Scheduled scripts
180
All other types
110

Notable specialty plugins in use: Custom GL Lines Payment Gateway Shipping Partners ×2 SDF installations ×10 — each represents deep platform coupling that must be re-solved on the target ERP.

⚠ The #1 migration risk in this account 465 RESTlets means an unknown number of external systems (e-commerce, EDI, 3PL, BI, middleware…) call into NetSuite programmatically. Every one of those endpoints must be found, its caller identified, and an equivalent built against the new ERP's API. Until this catalog exists, no migration estimate is credible. Recommended first action regardless of platform choice.

3Requirements — Derived From Actual Usage

These are not aspirational requirements; each maps to a feature or transaction type in live use in this account. Use this as your RFP scoring sheet and demand that vendors demo the Must rows with your data shapes, not canned demos.

RequirementPriorityEvidence in this instance
Multi-entity consolidation with elimination entitiesMUST6 subsidiaries incl. a dedicated US elimination subsidiary; consolidated parent
US + Canada + Vietnam localization (VAT filing, CAD/VND, statutory reporting)MUSTCA and VN operating subsidiaries; VAT Online configuration/submission permissions active
Discrete manufacturing: BOMs, work orders, WIP, assembly build/unbuild, costed BOMMUST252 WOs, 127 builds, WO issue/completion/close cycle, 50 assembly items, 9 unbuilds
Engineering change management (ECO)MUSTECO record types + implementation logs in use
WMS: multi-location, bin management, wave picking, lot/serial traceability, cycle countingMUST20 locations, 154 bins, 42 waves, 62 bin transfers, 130 lot/serial items, smart count configured
Full procurement workflow: requisitions → approvals → POs, blanket POs, vendor RFQs, vendor prepaymentsMUST3,894 POs; requisition, blanket PO, RFQ, and prepayment (VPrep/VPrepApp) transactions present
AR deduction & chargeback managementMUSTDeduction management module fully configured (tasks, write-off limits, setup)
Customer rebate management (agreements, tiers, settlements)MUSTRebate agreements, tier templates, settlement history, CSV rebate imports in use
Fixed asset management (depreciation, alternate methods, transfers, disposals)MUSTFull FAM module footprint (asset, depreciation history, proposals, R&M categories)
Revenue recognition (ASC 606)SHOULDRev arrangements/elements/plans visible (view-level) — confirm actual usage depth before scoring
Open, well-documented REST API + server-side extensibilityMUST465 RESTlets, 704 Suitelets, 206 Map/Reduce jobs — your team builds on the platform
Custom records / entities without codeMUST~567 non-bundle custom record types
Returns management (customer RMA + vendor return auth)SHOULD15 RMAs, 15 vendor return authorizations
Sales commissionsSHOULDCommission transactions present
Intercompany transfers / ownership transferSHOULDTransfer orders, inventory transfers, ownership transfer transaction
Light CRM: opportunities, quotes, activity trackingNICE27 opportunities, 13 estimates, 114 contacts — low usage; a bolt-on CRM is acceptable
Advanced document/PDF templatingNICEAdvanced Printing enabled; BOL preferences configured
Migration of ~2.5 yrs history + open balancesMUST~24K transactions since Dec 2023; masters in the low hundreds
The two "sleeper" requirements that will separate vendors Rebates and AR deductions/chargebacks. This combination usually means selling into retail/big-box or distribution channels with trade-spend complexity. Most mid-market ERPs handle these poorly or via third-party bolt-ons — make every vendor demo these two flows end-to-end with your tier structures before shortlisting.

4Candidate Platforms — Consider, Conditional, Avoid

Scored against the requirements above. Ratings are directional (based on general market capability, not a formal RFP) — validate with demos against your Must rows.

PlatformMfg + WMSMulti-entity / Intl.Rebates / DeductionsAPI / ExtensibilityFit for your sizeVerdict
Microsoft Dynamics 365 Business Central ●●●● ●●●● ●●●●● ●●●● ●●●●● CONSIDER
Acumatica ●●●● ●●●●● ●●●●● ●●●●● ●●●●● CONSIDER
D365 Finance & Supply Chain ●●●●● ●●●●● ●●●●● ●●●● ●●●●● IF GROWING
Epicor Kinetic ●●●●● ●●●●● ●●●●● ●●●●● ●●●● IF MFG-FIRST
Infor CloudSuite Industrial (SyteLine) ●●●●● ●●●●● ●●●●● ●●●●● ●●●● IF MFG-FIRST
SAP S/4HANA Public Cloud ●●●●● ●●●●● ●●●●● ●●●●● ●●●● HEAVY
Sage Intacct ●●●● ●●●● ●●●● ●●●●● ●●●●● AVOID
Odoo (Enterprise) ●●●●● ●●●●● ●●●●● ●●●● ●●●●● AVOID*
QuickBooks / Xero tier + bolt-ons ●●●● ●●●● ●●●●● ●●●●● ●●●● AVOID

✓ Consider — and why

Dynamics 365 Business Central — Best overall fit profile: solid discrete manufacturing and warehousing at your volumes, native multi-company consolidation, AL-language + API extensibility, and the largest partner ecosystem in the mid-market. Caveat: Vietnam localization is delivered via partner add-ons — verify a named, referenceable localization package before committing.

Acumatica — The closest cultural successor to NetSuite: true cloud, unlimited-user consumption pricing, genuinely open REST/OData APIs (your 465-RESTlet ecosystem will appreciate this), strong Manufacturing and WMS editions. Caveat: international localization is thinner out of the box; Vietnam would be partner-built.

D365 Finance & SCM — Only if you anticipate significant growth: natively strong exactly where you're unusual (trade allowances/rebates, deductions, global localizations incl. Vietnam) but a much heavier implementation and cost profile than BC.

✕ Avoid — and why

  • Sage Intacct (or any finance-first suite) — excellent GL/consolidation, but no real manufacturing or WMS; you would re-buy half your operational footprint as third-party bolt-ons with their own integration risk.
  • Odoo* — feasible on paper and cheap, but multi-entity eliminations + VN statutory compliance + rebates/deductions at your level means heavy custom development. You'd trade one 2,275-script customization pile for another, with less vendor accountability.
  • QuickBooks/Xero-tier stacks — categorically below your consolidation, manufacturing, and compliance needs.
  • Anything without a mature public API — disqualifying regardless of other strengths, given your integration surface.

5What the Migration Would Involve

An honest sizing, sequenced by dependency. The uncomfortable truth: for this account, integration archaeology precedes everything — including vendor selection, because the RESTlet/Suitelet catalog changes which platforms are even viable.

Phase 0 · Weeks 1–6 · do this before selecting anything

Integration & customization archaeology

Catalog all 465 RESTlets and 704 Suitelets: which are deployed and active, who calls them (check execution logs), what business function each serves. Triage the 8,060 custom fields and 655 custom record types into bundle-installed vs. in-house vs. dead. Rank in-house record types by live row count. Output: a definitive "what we actually built" register.

Phase 1 · Months 2–4

Selection & scripted demos

RFP scored against Section 3. Insist on demos of your hard flows: rebate tier settlement, AR deduction workup, ECO release, wave pick with lot capture, VN VAT filing, consolidated close with eliminations. Reference-check a customer of similar profile (multi-country manufacturer-distributor) for each finalist.

Phase 2 · Months 4–8

Core build & data migration design

Entity/COA design, item + BOM + routing migration, open-transaction strategy. Standard pattern: migrate masters, open transactions, GL balances by period; archive full history to a warehouse (this instance's ~24K transactions are trivially exportable to CSV/warehouse — I can produce those extracts on demand). Rebuild only the integrations and automations that survived Phase 0 triage.

Phase 3 · Months 8–12

Parallel run & phased cutover

Pilot with one US operating subsidiary first; Canada and Vietnam follow once localization is proven. Keep NetSuite read-only for a full audit cycle after cutover.

Months 12–18

Contingency

Multi-country manufacturing migrations of this shape rarely land under 12 months end-to-end. Budget to 18.

Risk register

RiskSeverityMitigation
Unknown external callers of 465 RESTlets break silently at cutoverHIGHPhase 0 catalog + execution-log analysis; deprecation window with logging before shutdown
Vietnam localization gap on the chosen platformHIGHNamed localization package + live customer reference required before contract signature
Rebate/deduction processes don't map to target ERPHIGHScripted demo with your real tier structures; budget for a specialist add-on (e.g. trade-spend ISV) as fallback
Custom-record business data (567 types) missed in migration scopeMEDRow-count ranking to find which types hold live data; explicit keep/archive/drop decision per type
Lot/serial genealogy lost in item migrationMEDMigrate on-hand lot/serial balances as opening state; archive full genealogy for recall lookups
Dual-maintenance fatigue during parallel runLOW-MEDPhase cutover by subsidiary; keep parallel window short and scoped

6Recommended Next Steps