Introduction
Finance stops trusting the numbers. Warehouse teams run compensating workflows. Marketing reports look useful but board reporting does not agree with cash in the bank. This is the moment DTC and omnichannel brands start talking about NetSuite: when turnover, subsidiaries and tax complexity reveal Brightpearl's limits and manual work spirals into reconciliation debt. This guide is for Operations Directors, Finance Directors and CTOs running £20m to £200m turnover who need a migration plan that avoids peak-trading collapse.
Quick answer
This NetSuite implementation guide explains how to move from Brightpearl to NetSuite without creating a dirty ledger or a month of reconciliation work. It covers operating-model design, the critical ownership decisions for items, inventory and financials, phased migration sequencing and the integration architecture you should design for Shopify, your WMS and payment gateways. The single most important reality is this: define and enforce a clear source-of-truth ownership model before you start migrating transactions. If you cannot answer who owns SKU price, stock on hand and tax treatment at every step, delay go-live until you can.
Cogent2 view: If finance cannot explain which system owns a SKU's price, stock and tax status, do not go live. You will create reconciliation debt that takes months to clear.
Executive summary
- Scope: Migration from Brightpearl (retail OMS + accounting) to NetSuite as the ERP and financial ledger for high-volume DTC retailers.
- Realistic duration: 22 to 30 weeks from discovery to first month-end in NetSuite.
- Biggest risk: source-of-truth ambiguity between Shopify, the WMS and NetSuite causing stock drift and settlement mismatch.
- Team shape: mix of internal project lead, NetSuite functional lead, middleware developer, data lead and finance owner.
- Budget shape: licensing, implementation partner fees and integration/middleware; internal resource backfill is often the largest hidden cost.
- Source-of-truth decision: NetSuite must be the item master and the financial authority; WMS must be the physical authority for stock.
- Single decision that determines success: clear ownership boundaries and an agreed cutover plan that freezes Brightpearl changes before delta migration.
Phase-by-phase breakdown
Below are practical phase cards. Each card lists duration, objectives, deliverables, owners, dependencies, risks and exit criteria.
Discovery and Architecture Design
| Duration | 4–6 weeks |
|---|---|
| Objectives |
|
| Deliverables | Process map, system architecture diagram, Functional Specification Document (FSD). |
| Owners | Project Lead, NetSuite Architect, Finance Lead. |
| Dependencies | Access to Brightpearl exports and Shopify API credentials. |
| Risks | Scope creep; unclear ownership causing design paralysis. |
| Exit criteria | Stakeholder sign-off on 'To-Be' operating model. |
Configuration and Build
| Duration | 8–12 weeks |
|---|---|
| Objectives |
|
| Deliverables | Configured NetSuite instance, middleware in UAT, mapping documents. |
| Owners | Implementation Partner, Middleware Developer, Finance Lead. |
| Dependencies | Discovery sign-off; test credentials for all systems. |
| Risks | Middleware rate limits and over-customisation that blocks upgrades. |
| Exit criteria | Successful smoke test of end-to-end data flows. |
Data Migration and UAT
| Duration | 6–8 weeks |
|---|---|
| Objectives |
|
| Deliverables | Cleaned migration templates, UAT logs, user manuals. |
| Owners | Data Lead, Finance Lead, Ops Lead, NetSuite Consultant. |
| Dependencies | Build completion and test data availability. |
| Risks | Dirty historical data polluting the ledger; UAT gaps. |
| Exit criteria | 100% pass rate on critical UAT scenarios and sign-off from finance. |
Cutover and Hyper-care
| Duration | 4 weeks post-go-live (hyper-care) |
|---|---|
| Objectives |
|
| Deliverables | Live NetSuite instance, hyper-care logs, first-week reconciliation report. |
| Owners | All stakeholders, on-call middleware and NetSuite support. |
| Dependencies | UAT sign-off and cutover communication plan. |
| Risks | High traffic days causing queue back-pressure and delayed postings. |
| Exit criteria | Successful first month-end close in NetSuite and acceptable KPI levels. |
Implementation timeline
| Phase | Duration | Critical-path note |
|---|---|---|
| Discovery & Architecture | 4–6 weeks | Chart of Accounts sign-off starts the critical path |
| Configuration & Build | 8–12 weeks | Item Master clean-up must finish before integration hardening |
| Data Migration & UAT | 6–8 weeks | End-to-end UAT gates go/no-go |
| Cutover & Hyper-care | 4 weeks | First successful month-end closes the critical path |
| Total | 22–30 weeks | Depends on data quality and number of subsidiaries |
Migration and implementation checklist
Operator-grade, copy-paste checklist. Run this every week in project stand-ups.
- Freeze Item Master changes in Brightpearl 14 days before cutover.
- Complete Chart of Accounts and tax nexus mapping; secure sign-off from Finance.
- Export Brightpearl item, customer and open-order datasets; run data quality checks.
- Confirm WMS location mapping to NetSuite locations 1:1.
- Implement middleware with queueing and retry logic to avoid spike failures.
- Run parallel test orders from Shopify into NetSuite and reconcile to expected G/L impacts.
- Execute full UAT scenarios: orders with partial shipments, refunds, exchanges, multi-currency sales.
- Schedule cutover weekend and communicate blackout windows to all teams.
- Perform delta migration and final inventory snapshot during cutover window.
- Post-go-live: run daily reconciliation of Shopify payouts to bank deposits for the first 4 weeks.
Implementation scorecard
Use this to assess go/no-go readiness. Mark each dimension Ready or Not Ready and provide evidence.
| Dimension | Ready looks like | Not ready looks like |
|---|---|---|
| Data quality | Item SKUs deduplicated; cost and revenue accounts mapped. | Duplicate SKUs, missing costing, inconsistent tax codes. |
| Integration maturity | Middleware handles queues, retries and mapping; test webhooks pass. | Ad-hoc CSV imports, no retry logic, unclear error handling. |
| Operational discipline | Warehouse follows single source for adjustments; no local CSVs. | Warehouse teams run local spreadsheets and manual adjustments. |
| Change appetite | Teams allocated time for training and process change. | Project seen as IT change only; no business time allocated. |
| Exec sponsorship | Board sponsor assigned and engaged in cutover decisions. | No senior sponsor; decisions stall in working groups. |
| Finance ownership | Finance Lead owns Chart of Accounts and UAT finance scenarios. | Finance peripheral to decisions; reconciliation left to ops. |
Risks and mitigations
| Risk | Severity | Mitigation | Owner |
|---|---|---|---|
| Source-of-truth ambiguity causing stock drift | Critical | Define NetSuite as financial authority; WMS as physical authority; enforce write paths. | Technical Architect |
| Migration of dirty historical data | High | Migrate open balances only; use summary journals for prior periods; archive Brightpearl transaction history. | Data Lead |
| Finance learning curve on journals | Medium | Allocate Finance Lead and deputy; run sandbox month-end practice runs. | CFO / FD |
| Over-customisation breaking upgrades | High | Prefer configuration over scripting; limit SuiteScript to unavoidable gaps. | Implementation Partner |
What breaks at scale
| Symptom | Cause | Impact | Prevention |
|---|---|---|---|
| Sync latency during peaks | Middleware and scripts queue back-pressure | Orders backlog; delayed fulfilments | Design event-driven architecture with queueing and throttling |
| Reconciliation debt | Manual CSV adjustments bypassing integrations | Month-end takes weeks; decision-making delayed | Governance: all adjustments originate in the WMS and flow via integrations |
| Settlement drift | Payouts mapped to orders without fees/refunds accounted | Bank vs ledger never reconciles | Design settlement reconciliation: aggregate payouts and match to journals |
Cogent2 view: High-volume brands underestimate settlement mapping. If payouts are treated as order-level cash, you will need a team to reconcile for months.
Hidden costs
- Data cleansing contractor for Brightpearl historical orders: dedicated cost often required.
- Middleware tier upgrades when order volume exceeds initial estimates.
- Custom NetSuite reporting and Saved Searches for board and HMRC reporting.
- Internal backfill for Project Lead and Finance Lead during peak project months (£40k–£80k typical).
- Post-go-live training and on-premise floor walkers for warehouse teams.
Team requirements
| Role | FTE | When involved |
|---|---|---|
| Internal Project Lead (Ops or Finance) | 1.0 | Entire project duration |
| Finance Lead (Ledger design) | 0.5 | Discovery, UAT |
| NetSuite Functional Consultant (external) | 1.0 | Build and Migration |
| Middleware / Integration Developer (external) | 0.5 | Configuration, Cutover, hyper-care |
| Data Lead | 0.5 | Migration and UAT |
Budget expectations
Realistic ranges and what moves them.
| Area | Range | What increases cost |
|---|---|---|
| NetSuite licensing and modules | £30k–£110k pa | Advanced Inventory, WMS, multiple subsidiaries increase licence fees |
| Implementation partner fees | £50k–£250k one-off | Complex customisations and number of subsidiaries |
| Integration / middleware | £10k–£40k pa | High order volumes, custom connectors, SLA requirements |
| Internal resource backfill | £40k–£80k estimated | Length of project and seniority of resources |
| Contingency | 20% | Data issues and scope creep |
Integration dependencies
| System | Direction | Criticality | Notes |
|---|---|---|---|
| Shopify | Bi-directional | Critical | Order capture; refunds and payouts must map to NetSuite journals. |
| WMS / 3PL | Bi-directional | Critical | Physical authority for inventory; fulfilment status and stock adjustments flow to NetSuite. |
| Payment gateways (Stripe, Adyen) | Inbound | High | Settlement and fee data required for reconciliation. |
| Klaviyo / CRM | Outbound | Medium | Customer and purchase history for marketing segmentation. |
| Middleware / iPaaS | Orchestration | Critical | Queueing, retries and transformation. Confirm vendor and SLA before build. |
Source-of-truth ownership
| Data object | Owning system | Downstream consumers |
|---|---|---|
| Item master (SKUs, pricing) | NetSuite | Shopify, WMS, Klaviyo |
| Inventory levels (available to promise) | WMS / 3PL | NetSuite (sync), Shopify (via NetSuite) |
| Order capture | Shopify | NetSuite, Payment Gateways |
| Financial ledger, COGS, tax | NetSuite | BI, Board reporting, HMRC |
| Returns and refunds | NetSuite (finance) and WMS (physical) | Shopify, Finance team, Warehouse |
Operational readiness checks
- ✓ Finance can complete a full month-end close in the sandbox.
- ✓ Warehouse can pick, pack and manifest 100 orders in UAT without manual intervention.
- ✓ Shopify test orders flow to NetSuite and create correct G/L impact.
- ✓ All 3PL inventory locations mapped 1:1 to NetSuite.
- ✓ User permissions prevent shadow workflows and CSV bypasses.
Cutover planning
Pre-cutover
- Freeze Item Master changes in Brightpearl 14 days prior.
- Pre-load customers and static data into NetSuite.
- Validate that open Goods Out notes in Brightpearl are complete or cancelled.
- Staff training certification required for login access during cutover.
Cutover window (example sequence)
- Friday 18:00: Disable Shopify-Brightpearl sync and lock Brightpearl.
- Saturday 09:00: Final stock take and delta export.
- Sunday 10:00: Import deltas into NetSuite in staging; run smoke tests.
- Monday 06:00: Enable NetSuite-Shopify integration for live traffic.
Post-cutover
- On-site floor walkers for warehouse teams for 2 weeks.
- Daily reconciliation of Shopify payouts to NetSuite bank deposits for 4 weeks.
- Weekly technical-debt logs and prioritisation sessions.
Rollback planning
Trigger conditions
- Integration failure impacting more than 10% of orders.
- Critical inventory mismatch discovered during delta reconciliation.
- WMS failing to acknowledge fulfilment requests from NetSuite.
Rollback steps
- Disable NetSuite integrations and stop new writes.
- Re-enable Brightpearl-Shopify and Brightpearl-WMS syncs.
- Import interim orders placed during cutover into Brightpearl via CSV and reconcile.
- Communicate delay and next steps to stakeholders and customers if required.
Data reconciliation checkpoints
- Compare last Brightpearl Sales Order ID with first NetSuite Sales Order ID.
- Take inventory snapshots before and after cutover and reconcile locations.
Post-go-live and hypercare
Hypercare weeks: 4. Focus on stabilisation and knowledge transfer.
| KPI | Target |
|---|---|
| Sync error rate | <0.5% |
| Time to month-end close | <5 days |
| Inventory variance (WMS vs NetSuite) | <1% |
Stabilisation actions
- Weekly integration health checks and error triage.
- Refine Saved Searches and operational reports for daily use.
- Sunset Brightpearl access and enforce NetSuite-only workflows.
Common failure modes
| Failure | Prevention |
|---|---|
| Reconciliation debt accumulation | Map every Shopify transaction to GL accounts and run settlement reconciliation daily during hypercare. |
| Over-customisation trap | Use configuration where possible; limit SuiteScript to gaps that cannot be addressed by business process change. |
| Inventory latency drift | Make the WMS the inventory authority and ensure timely stock adjustments via the integration. |
Cogent2 view: NetSuite is a ledger first. If you treat it like a flexible OMS, you will inherit the same operational mess and add cost.
Decision matrix
When to DIY, when to hire, when to delay or consider alternative platforms.
| Scenario | Do it yourself | Hire a partner | Delay | Replatform instead |
|---|---|---|---|---|
| Small catalogue, low order volume, no subsidiaries | ✓ | |||
| Multiple subsidiaries, complex tax, high order volume | ✓ | |||
| Poor data quality and no finance ownership | ✓ | ✓ | ||
| Need simpler ledger and minimal change | Consider lighter ERP or improved Brightpearl setup |
The Cogent2 view
NetSuite is not a bigger Brightpearl. It is a formalisation of your commercial controls. Projects succeed when the business accepts stricter processes and the team designs ownership boundaries before data moves. Focus on the finance trust boundary, the item master and the physical inventory authority. Build integrations with queueing, retries and observable error handling. Budget realistically for internal backfill; that is the cost most teams miss.
Cogent2 view: Do a 'Source of Truth' audit 8 weeks before go-live. If you cannot answer who owns price, stock and tax per SKU at every lifecycle stage, pause the project.
Cogent2 view: Settlement reconciliation is the quiet failure mode. Design to reconcile payouts to journals from day one, not month three.
Frequently asked questions
When should our business consider moving from Brightpearl to NetSuite?
Typically when turnover exceeds about £20m, you add subsidiaries or multi-currency tax complexity, or manual reconciliations at month-end become a recurring operational drag.
Can we migrate all Brightpearl historical transactions into NetSuite?
Avoid migrating every transaction. A pragmatic approach is: migrate current balances and open transactions, bring prior-period totals via summary journals and archive Brightpearl for deep-history lookups.
Who should own the Item Master after migration?
NetSuite should own the Item Master for pricing, GL mapping and product attributes; the WMS should be the physical authority for stock levels.
How long does a typical implementation take?
Realistically 22–30 weeks from discovery to first month-end close, depending on data quality, number of subsidiaries and integration complexity.
What are common hidden costs we should budget for?
Data cleansing contractors, middleware tier upgrades, custom reporting, and internal backfill for the Project Lead and Finance Lead are common overlooked costs.
Do we need middleware or can we use point-to-point connections?
High-volume implementations should use middleware with queueing and retry capabilities. Point-to-point connections often create the 'sync illusion' and fail under load.
How do we prevent stock drift during cutover?
Freeze Item Master changes, complete all Goods Out notes, take a final inventory snapshot, and enforce the WMS as the inventory authority during the delta migration.
What KPIs should we monitor during hypercare?
Monitor sync error rate (<0.5%), time to month-end close (<5 days) and inventory variance (WMS vs NetSuite <1%).
Final call to action
If you are preparing to move from Brightpearl to NetSuite, book a NetSuite Readiness Audit. We will diagnose your source-of-truth ambiguity, map the order-to-cash critical path and identify the single changes that reduce reconciliation debt before you purchase licences or choose a partner.