A comprehensive netsuite migration checklist covering pre-migration assessment, design sign-off, extract/transform/load, reconciliation per subsidiary per book, parallel-run delta replay, cutover and post-cutover hyper-care. Every item has saved a real project from a real failure mode. Use it as a gate, not a wish-list.
The difference between a netsuite migration checklist that lands a project and one that becomes a forgotten doc is enforcement. Treat each phase as a gate: 100% complete or you don't advance. Treat each item as evidence-required: signed off by an accountable person.
Most NetSuite to Oracle Fusion migrations have a checklist. Most still overrun by 25–50%. The checklist itself isn't the problem — the discipline around it is. Teams check items 'done' when they're 80% done. Teams skip items because 'we'll do that later.' Teams sign off without evidence. By week 18, the checklist is a fiction and the project is reverse-engineering its way back to a plan.
The netsuite migration checklist on this page is built to be enforced. Each item has an owner role (Functional Lead, Tech Lead, Data Lead, Finance Sign-Off, Compliance Sign-Off, PMO), an evidence artefact (the document, screenshot, signed pack, log file that proves the item is complete), and a phase gate (Assessment, Design, Sandbox, Parallel-Run) where it must be complete before the project advances. Syntra ETL projects don't advance past gate boundaries without 100% completion of in-scope items. That's how we hit 8% overrun rate vs 45% industry.
The checklist is structured in six phases with 60+ items. Industry verticals (SaaS, distribution, manufacturing, professional services) extend the base checklist with 10–20 additional items each — handled by vertical-specific extensions Syntra ETL ships alongside the base. The post-cutover hyper-care and decommissioning sections often get neglected in other checklists; we treat them as first-class because the SOX 7-year retention window and NetSuite subscription renegotiation matter to multi-year ROI.
Complete before any design decision. Inventory drives design — never the reverse.
TBA or OAuth 2.0 credentials issued with read-only integration role. SuiteAnalytics Connect ODBC connection validated. SuiteTalk REST v1 + SOAP endpoints reachable.
Complete subsidiary tree including elimination subs and inactive subs. Base currency per sub captured. Inter-company partner matrix exported. Consolidation hierarchy documented.
Every CUSTOMRECORD walked. Parent-child relationships mapped. Referential dependencies to standard records identified. Usage frequency captured.
SCRIPTDEPLOYMENT catalog complete: User Event, Client, Scheduled, MapReduce, RESTlet, Suitelet, Workflow Action. Last-run-date and status per deployment.
Every active SuiteFlow workflow exported. State machine definitions captured. Trigger events documented. Business purpose classified.
SAVEDSEARCH metadata complete. Run-frequency per search captured. Semantic clustering for duplicate identification. Critical-path subset identified.
Every active arrangement → elements → obligations → recognition events. Remaining deferred revenue per obligation. Recognition calendar per obligation.
Every active book (Primary, IFRS Adjustment, US Tax, Local Tax, Management) catalogued. Accounting representation rules documented. Posting volume per book per period sized.
The build phase. Each item gated by signed-off evidence before advancing.
Ledger/LE/BU/Inventory Org structure designed from OneWorld evidence. Base currencies assigned to Primary Ledgers. Finance, ops, IT sign-off.
NetSuite Subsidiary + Department + Class + Location + Custom Segments → Fusion 6-segment COA. Posting-level validation against production journals. Finance sign-off.
Each Custom Record: retire / route to Fusion DFF / route to EFF / route to App Composer / route to OTBI subject area. Justified by business purpose. Tech Lead sign-off.
Each SuiteScript: retire (Fusion native handles) / rebuild as AMX workflow / rebuild as OIC integration / rebuild as App Composer Groovy / rebuild as ESS process. Tech Lead sign-off.
Each surviving Saved Search: auto-convert to OTBI / manual rebuild in OTBI / rebuild in BI Publisher. Prioritized by run-frequency. Finance sign-off on critical path.
Synthetic recognition run in Fusion sandbox. Opening balance per obligation matches NetSuite closing balance cent-for-cent. Compliance sign-off.
Trial balance per book per subsidiary per period, AR aging, AP aging, inventory valuation, ASC 606 deferred revenue — sandbox vs NetSuite source matches to the cent.
Full production FBDI/HDL load executed. Reconciliation per book per subsidiary per period green. Sign-off pack drafted ready for stakeholder review.
The final phases. Each item has saved a real project from a real failure mode at go-live.
Production load fully reconciled per book per subsidiary per period. Sign-off pack drafted. ASC 606 cent-level validation green. Multi-book trial balances match. AR/AP aging match. Inventory valuation matches. Stakeholder review begins.
Both systems live for the period. Daily delta replay from NetSuite to Fusion. Daily reconciliation. End-of-period: full reconciliation per book per subsidiary, stakeholder review, variance investigation if any. Sign-off per subsidiary per book.
Second parallel period. Same delta replay and reconciliation cadence. End-of-period: full reconciliation, sign-off pack finalized, internal audit review, cutover authorization decision. If green: proceed; if red: investigate and re-parallel.
Final delta capture (transactions since last reconciled period close). Replay to Fusion. NetSuite to read-only mode. User cutover to Fusion. Integration cutover (CRM, payroll, banking) to Fusion endpoints. Production transactions flow to Fusion only.
Dedicated war room: technical, functional, Syntra ETL on-call. Defect triage SLA 2 hours. Root-cause documented within 24 hours. Fix deployed within 72 hours. Daily reconciliation continues. NetSuite read-only accessible for cross-reference. Weekly stakeholder sign-off.
NetSuite subscription renegotiated to archive-only (typically 15–25% of full). Or Syntra ETL long-term archive deployed and NetSuite fully terminated. SOX 7-year retention plan in place. OAuth credentials revoked. Integration endpoints torn down. Final contract end-date set.
Vertical-specific items that extend the base checklist. Required if your operation includes the vertical.
ASC 606 multi-element arrangements with services + licence + support + usage. Subscription billing schedules. Usage-based metering data. Deferred revenue per obligation. Contract modifications mid-stream.
Item costing method per inventory org (Average/FIFO/LIFO/Standard). Inventory valuation snapshot per location. Demand planning data. MRP horizon. Drop-ship transactions.
BOMs (multi-level). Routings. Work orders (assembled and in-flight). Assembly builds. Component issue history. Production WIP.
Projects with phases/tasks. Resource allocations. Time entries. Expense reports. Project billing schedules. Percent-of-completion data.
Web store catalogue. Online customer master. Web order history. Payment tokenization data. Subscription/recurring billing schedules.
Employee master with effective-dated history. Time tracking history. Basic payroll history (US/CA/AU). Time-off balances. Performance review history (if used).
A complete netsuite migration checklist runs 60+ items across six phases: Pre-Migration Assessment (account access, role provisioning, OneWorld subsidiary inventory, Custom Record catalog, SuiteScript inventory, Saved Search export, ASC 606 portfolio extract, multi-book inventory, integration inventory, data volume sizing), Design (enterprise structure design, COA crosswalk, Custom Record routing, SuiteScript retire/rebuild plan, Saved Search rebuild plan, ASC 606 continuity plan, multi-book strategy, security/role design), Extract (TBA/OAuth credentials, SuiteAnalytics Connect ODBC connection, REST/SOAP endpoint validation, governance-unit budget, partition strategy), Transform/Load (FBDI/HDL payload generation, validation pre-Fusion-submit, sandbox load and reconcile, production load), Reconcile (trial balance per book per subsidiary, AR/AP aging, inventory valuation, ASC 606 deferred revenue, multi-currency revaluation), and Cutover (parallel-run delta replay, sign-off pack, NetSuite read-only mode, hyper-care war room).
Three NetSuite-specific concerns dominate. (1) OneWorld multi-subsidiary mapping items: subsidiary tree, base currencies per sub, elimination subs, inter-company partner matrix, consolidation hierarchy. (2) Customization inventory items: Custom Records, Custom Fields, SuiteScript 2.x/2.1 deployments, RESTlets, Suitelets, SuiteFlow workflows, Saved Searches, KPI Scorecards, SuiteAnalytics Workbooks, Custom Forms. (3) ASC 606 continuity items: Advanced Revenue Management arrangement portfolio, performance obligation chain, recognition calendar, deferred revenue per obligation. A generic ERP migration checklist misses these — the netsuite migration checklist must address them explicitly or the project blows up in week 18.
Continuously, but with formal review gates at four milestones: (1) End of Assessment (week 3) — Pre-Migration items must be 100% complete; sign-off blocks transition to Design. (2) End of Design (week 5) — Design items must be 100% complete and approved by finance, ops, IT; sign-off blocks transition to Build. (3) End of Sandbox Load (week 11) — Transform/Load items must be 100% complete with sandbox reconciliation green; sign-off blocks transition to Production Load. (4) End of Parallel-Run (week 17) — Reconcile and Cutover items 100% complete with sign-off pack per subsidiary per book; sign-off authorizes cutover. The checklist is a gate, not a wish-list.
Five items teams routinely miss until late. (1) RESTlet inventory — RESTlets are often built for non-NetSuite-user integrations (mobile apps, third-party systems) and don't surface in standard SuiteScript audits. Always: query SCRIPTDEPLOYMENT WHERE SCRIPTTYPE = 'RESTlet'. (2) SuiteFlow workflow inventory — workflows often live alongside SuiteScript but in a separate catalog. (3) Multi-book Adjustment book inventory — finance teams often forget the IFRS Adjustment book or US Tax book until reconciliation reveals it. (4) Inter-company elimination rules — OneWorld auto-eliminates inter-company; Fusion AGIS rules must be explicitly built. (5) ASC 606 percent-of-completion arrangements — different from straight subscription recognition, often missed in obligation portfolio extract.
Custom Fields are NetSuite's lightest customization — added to standard records (Customer, Item, Transaction, etc.) to capture business-specific data. They typically number in the hundreds in mature accounts. The checklist item: query CUSTOMFIELD metadata via SuiteAnalytics Connect for every standard record type, capture field ID, label, data type, applies-to record, usage frequency (via Saved Search referencing the field), and source (manual entry vs SuiteScript-populated vs integration-populated). Each Custom Field gets a routing decision: business-critical → Fusion DFF on the equivalent record; analytical-only → OTBI custom subject area; legacy/abandoned → retire. Typical outcome: 40–60% of Custom Fields retire as unused or duplicative.
Yes — and it's frequently the highest-risk item because integrations span beyond NetSuite admin visibility. The checklist requires: (1) Outbound integrations — every SuiteScript-initiated REST call, every scheduled CSV export, every SuiteCommerce/SuiteCommerce Advanced data feed. (2) Inbound integrations — every TBA/OAuth credential issued to third parties (CRM, payroll provider, banking, payment processor, EDI, tax engine, expense management). (3) Native NetSuite connectors — Bronto, Endeca, SuiteCommerce Advanced. (4) Custom RESTlets exposed to external consumers. Each integration gets a retire/rebuild/route decision for the Fusion target: rebuild as OIC integration flow, route to Oracle Cloud Integration, or retire if Fusion native handles the use case.
Verticals require additional checklist items. SaaS/Software: ASC 606 multi-element arrangements, subscription billing schedules, usage-based metering data, deferred revenue per obligation. Distribution/Wholesale: item costing method (Average/FIFO/LIFO/Standard), inventory valuation per location, demand planning data, MRP horizon. Light Manufacturing: BOMs (multi-level), routings, work orders (assembled and in-flight), assembly builds. Professional Services/PSA: projects, tasks, resource allocations, time entries, expense reports, project billing schedules, percent-of-completion data. Each vertical extends the base 60-item checklist with 10–20 vertical-specific items. Syntra ETL ships pre-built vertical checklists alongside the base netsuite migration checklist.
Cutover is not the end — hyper-care and decommissioning continue the checklist. Hyper-care items (weeks 1–4 post-cutover): defect triage SLA met, daily reconciliation continues, NetSuite read-only access maintained, weekly stakeholder sign-off. Knowledge transfer items (weeks 2–6 post-cutover): runbooks delivered to BAU team, OTBI/BI Publisher report inventory documented, OIC integration documentation, role/security documentation. NetSuite decommission items (months 2–24): NetSuite subscription renegotiation (archive-only typically 15–25% of full), final SOX 7-year retention plan executed (Syntra ETL long-term archive or NetSuite archive-only contract), inactive user cleanup, integration teardown, OAuth credential revocation, final NetSuite contract termination on the SOX retention end-date.
Book a 30-minute discovery call. We'll customize the netsuite migration checklist to your scenario (OneWorld scope, customization depth, industry vertical, multi-book setup, ASC 606 complexity) and walk through it together — even if you're not engaging Syntra ETL for delivery. The checklist is yours to keep.