Plan an ERP rollout in phases while the business keeps serving customers
ERP

Plan an ERP rollout in phases while the business keeps serving customers

Worktechlabs editorial team 22 September 2026 7 min read
Plan an ERP rollout in phases while the business keeps serving customers

A growing business may need a new ERP while still taking orders, serving customers and closing the month. Replacing everything at once can concentrate uncertainty into a single launch. A phased rollout can reduce the scope of each transition, provided every phase supports a complete piece of business and the boundaries between systems are deliberately managed.

Phasing is a delivery strategy, not a guarantee of low risk. It exchanges one large transition for several smaller transitions and a period of coexistence that needs its own design.

Which processes justify a bespoke ERP module?

A bespoke module is worth considering when an important, repeated process cannot be handled adequately through standard configuration or a dependable integration. Examples might include allocating specialist crews against contractual rules, pricing a configurable manufacturing order or tracing customer-owned stock across several locations. These are illustrative scenarios, not evidence that every business with those activities needs custom software.

Show the gap using actual transactions: the rule a standard product cannot express, the workaround people use and the consequence for customers or staff. Compare adapting the process, configuring an existing product and developing the missing capability. An unusual screen layout alone rarely explains the lifetime responsibility of maintaining custom business logic. Microsoft's process-based implementation guidance offers a useful reference for expressing scope through business outcomes.

Choose the smallest custom responsibility that resolves the gap. A specialist planning module can work alongside existing accounting; it does not automatically justify rebuilding purchasing, invoicing and every report. Record which system remains authoritative for each shared record.

How should you size the first ERP module?

Select a coherent group of transactions, a business unit or a service journey. The first phase should allow users to complete useful work from beginning to end. Launching order entry without a dependable route to fulfilment may create a demonstration milestone while forcing staff into more manual coordination.

Consider shared dependencies before choosing the boundary. Customer records, product data and reporting may span several teams even when only one location moves first. Identify who owns each shared fact during coexistence. A phase that looks small on an organisational chart can still touch most of the business's information flows.

Write a first-module brief with a named user group, a trigger, a completed outcome, essential exceptions and the systems it touches. Size the work using transaction volumes, rules, permissions, integrations and data quality, as well as screens. For example, accepted order → resource allocation → confirmed job is a reviewable slice; “the scheduling screen” leaves the surrounding work undefined. Ask for assumptions and exclusions in the estimate, then validate the most uncertain integration before committing to a delivery date.

Which data needs to move for the first phase?

Prepare a migration register with an owner, source, destination and acceptance check for each data group:

  • Master records: active customers, products, units, sites and references required by the first workflow.
  • Open work: the selected orders, reservations, balances or projects that must continue in the new module.
  • Rules and access: applicable price agreements, approval limits, user roles and reference mappings.
  • History and attachments: the records needed for service, reporting or agreed retention; decide what can remain in a searchable archive.

Confirm these choices with the people responsible for operations and records. Do not copy every table simply because an export is available. Reconcile relationships and relevant totals, test difficult records, and plan how changes made after the trial export will reach the final migration. Microsoft's data-management guidance covers migration and quality within the wider data lifecycle.

Decide where existing work will finish

Open orders and projects need an explicit treatment. Some may finish in the old system; others may move with their history and current state. Choose based on business requirements and the ability to reconcile the transition, rather than assuming every historical record must be migrated immediately.

An illustrative distributor might start new orders for one product family in the new ERP while completing older orders in the previous system. Staff then need a reliable way to locate an order and explain its status. The customer should not have to understand the migration plan to get a useful answer about their purchase.

Design the coexistence period

Document which system owns new transactions, how shared data moves and what prevents duplicate processing. If a customer changes an address, the update must follow an agreed route. If an order is cancelled, both systems must not continue treating it as active because each assumes the other will handle the change.

Set a plan for retiring temporary integrations and manual reconciliations. A temporary bridge can become permanent if later phases are delayed, so its support responsibility still matters. Include the cost and effort of coexistence when comparing a phased approach with a broader launch. Smaller releases can be easier to absorb while still requiring significant coordination overall.

Rehearse the transition with business users

Test representative transactions, migrated data and ordinary permissions. Include a correction, a return, a failed integration and a customer question about work started before the transition. The people who will operate the system should demonstrate the journey, rather than watch the implementation team complete it with elevated access.

Microsoft's go-live checklist and transition guidance provide useful preparation references. Use them to identify the areas that need evidence, then adapt the checks to your scope. A completed technical deployment is only one part of readiness; users, data and support must also be prepared for the specific business phase going live.

Set clear conditions for proceeding

Agree what must be true before launch: important workflows work, data has been reconciled, staff can perform their tasks and support can investigate problems. Record unresolved issues with their consequences and owners. “Nearly ready” is difficult to assess without agreed conditions.

Prepare a response if the transition does not behave as expected. Depending on the work already processed, restoring the old application may not be enough; new orders and external actions may need reconciliation. Define a realistic recovery decision with the business, including who can pause intake and how customers will be informed if service is affected.

Learn before expanding the next phase

After launch, review completed work, errors, support demand and the quality of customer information. Give the team time to stabilise normal operations before adding another substantial change. A calendar target alone is not evidence that the first group can support an expansion.

Use findings to adjust training, configuration and the next phase's scope. A pilot may reveal that the chosen process differs across locations or that a shared data rule needs revision. Treat this learning as part of the strategy. Phasing creates value when the business uses early evidence to improve later decisions.

Plan a practical rollout with Worktechlabs

Begin with the business outcome, map shared dependencies and compare possible phase boundaries. Produce a first scope that can complete real transactions, a coexistence plan and clear launch criteria. Include operational ownership so the new system can be maintained after the implementation team steps back.

Worktechlabs can help plan ERP change and the integrations needed during transition. Tell us which operations must keep running while your systems change. We can help define a phased approach that prepares the business for growth while making the work, decisions and transition responsibilities visible from the start.

Check the business case before the first phase

If you have not yet chosen an approach, compare bespoke ERP with off-the-shelf software for UK SMEs. Then use the ERP development cost guide to check whether the first-phase estimate includes migration, integrations, testing and costs after launch.

Official sources and further reading

ERPCRMB2B
Worktechlabs

Written by

Worktechlabs editorial team

About the team and our articles

Want to discuss this with the team?

We are happy to talk through how this applies to your own system.

Get in touch

Let's talk

What would you like to improve in your business?

Discuss your project 020 3883 2194

We use cookies

Necessary cookies keep the site working. With your permission we also use analytics cookies. Google receives basic measurement signals without analytics cookies before you accept or if you reject. You can change your cookie choice at any time. See our cookie policy.

Privacy settings

Cookie preferences

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.