What should I prepare before a NetSuite implementation starts?

Settle the structure first: subsidiary hierarchy, currencies, tax nexuses, chart of accounts and segment design, plus which data you will migrate and its quality. Name an owner who can approve each phase gate. These decisions are expensive to change once the build begins.

What are the phases of a NetSuite OneWorld implementation?

Discovery, design, build, data migration, test, go-live and hypercare. Each phase has an entry gate, deliverables and an exit sign-off before the next begins, which is what protects the OneWorld foundations that are costly to undo.

What is the most common reason NetSuite go-lives fail?

Decisions, not technology: scope found late, data migrated before the structure is settled, and testing compressed to hold a date. A gated method with clear approvers and reconciled opening balances prevents most of it.

NetSuite implementation checklist for a OneWorld go-live

A successful NetSuite OneWorld implementation runs as gated phases - discovery, design, build, migration, test, go-live and hypercare - each with an owner who signs it off before the next begins. The work that decides success happens before the build: settling the subsidiary structure, currencies, chart of accounts and tax, and cleaning the data you will migrate.

Before you start

Most implementation pain is decided before anyone configures anything. Have these settled first:

The subsidiary hierarchy, base currencies and tax nexuses - the structure that is expensive to change later.
The chart of accounts and segment design (class, department, location) you actually want to report on.
Which data you will migrate - opening balances only, or history - and the state of the source data.
The integrations in scope, and the owner who can approve each phase gate without delay.
A clear go-live date and the close you are cutting over around.

The gated phases to run

Run the implementation as seven phases, each with an entry gate, deliverables and an exit sign-off:

Discovery - requirements, entity structure, fit-gap.
Design - subsidiaries, currencies, chart of accounts, tax, Multi-Book.
Build - configuration, roles, workflows, scripts.
Data migration - master data and opening balances, reconciled to source.
Test - system and user acceptance testing, intercompany and consolidation.
Go-live - cutover, final loads, go/no-go, rollback ready.
Hypercare - first-close support and handover.

Pitfalls that derail go-live

The recurring failures are predictable, and avoidable:

Migrating data before the structure that holds it is settled, so balances never tie.
Discovering a subsidiary, currency or tax nexus mid-build, after the foundation was designed without it.
Compressing or skipping testing of intercompany, consolidation and multi-book to hold a date.
No agreed re-baseline when scope changes, so the plan quietly becomes fiction.
No reconciliation of opening balances to source before go-live.

Frequently asked questions

What should I prepare before a NetSuite implementation starts?: Settle the structure first: subsidiary hierarchy, currencies, tax nexuses, chart of accounts and segment design, plus which data you will migrate and its quality. Name an owner who can approve each phase gate. These decisions are expensive to change once the build begins.
What are the phases of a NetSuite OneWorld implementation?: Discovery, design, build, data migration, test, go-live and hypercare. Each phase has an entry gate, deliverables and an exit sign-off before the next begins, which is what protects the OneWorld foundations that are costly to undo.
What is the most common reason NetSuite go-lives fail?: Decisions, not technology: scope found late, data migrated before the structure is settled, and testing compressed to hold a date. A gated method with clear approvers and reconciled opening balances prevents most of it.

Last reviewed: 2026-06-27 by Wouter Nortje, CA