Contents
Your question in detail?

A senior-led conversation gets to the heart of your situation.

Before go-live, an ERP implementation needs answers in six phases: steering before the start (goal, decision-maker, budget including internal effort), processes and requirements (standard before customisation, interfaces, AI use cases), system and partner (demo on your own processes, names in the team, running costs), data and migration (master data measured, owners, two trial migrations), testing and training (real cases, roles, acceptance) and go-live and operations (go/no-go four to six weeks ahead, cutover rehearsal, support until the first month-end close).

How to use this checklist

The items follow the six phases of an implementation. Each item is worded so that it can be answered with yes or no. A no is not a drama, but an open decision with a name and a date. The only dangerous items are those where nobody knows who is supposed to answer.

Phase 1: Before the project starts

  • The goal is set in business terms. Not “a new ERP”, but what runs faster, safer or cheaper afterwards, such as the month-end close, delivery capability or order entry.
  • A decision-maker with time is named. Management sits on the steering committee, the internal project lead is released for a fixed share of time, not on the side.
  • The budget includes the internal effort. Key users, data maintenance, testing and training cost your own time. Whoever only counts licence and partner calculates too tightly.
  • Success criteria are measurable. How you will recognise in six months that the implementation was worth it is written down.
  • The escalation path is clear. Who decides when the department and the partner cannot agree, and by when.

Phase 2: Processes and requirements

  • The core processes are described, as-is and to-be. From quote to payment, from purchasing to warehouse, with the exceptions that really occur.
  • Standard before customisation is agreed. Every deviation from the standard needs a business reason, not a habit.
  • Requirements are prioritised. Must, should and could are separated, and every must has an owner in the department.
  • All interfaces are listed. Web shop, banks, EDI, warehouse management, time recording, payroll: with direction, frequency and owner.
  • The AI use cases are named. Two processes that cost the most manual work today, such as incoming invoices or orders from e-mails. What Business Central brings for this is described in Business Central agents and Copilot.

Phase 3: System and partner

  • The system was demonstrated on your processes. A demo following your script with your examples, not the standard vendor presentation.
  • You know the names in the project team. Who at the partner will actually consult and develop, and how much of that is senior experience.
  • The running costs are calculated. Licences per user, apps, support and further development. The list prices are in Business Central licence cost.
  • Cloud or on-premises is a deliberate decision. Copilot and the agents only exist in Business Central online. What that means for on-premises is described in AI for Business Central on-premises.
  • The contract governs changes. How new requirements are assessed, approved and invoiced, before the first one appears.

Phase 4: Data and migration

  • The master data is measured. Duplicates, empty mandatory fields and inactive records are counted before anyone cleans up. How to go about it is described in Cleansing master data before the ERP migration.
  • Every data area has an owner. Items, customers, suppliers, bills of materials, prices: one person from the department each, not IT.
  • It is decided what gets migrated. Open items and balances yes, the full history usually not. Access to the legacy system for audits and retention periods is settled.
  • At least two trial migrations are planned. The first shows the major errors, the second whether they are fixed.

Phase 5: Testing and training

  • The test cases come from real business transactions. Real orders, real special cases, real quantities, not invented examples.
  • End-to-end tests have run. From order to payment and from purchasing to posting, across all interfaces.
  • Roles and permissions are tested. Everyone only sees and posts what they should. That also applies to AI functions, because they work with the permissions of the user.
  • Key users are trained and train others. They know their area in the new system better than the partner and are the first point of contact on go-live day.
  • Acceptance is documented. Signed per process by the owner in the department, with a list of open items.

Phase 6: Go-live and the weeks after

  • Go/no-go criteria are written down. The decision is made four to six weeks before the date. How to recognise readiness is described in Business Central go-live: how do I know whether we are ready?
  • The cutover has been rehearsed. Sequence, responsibilities and fallback plan have been run through in a dress rehearsal.
  • Support after go-live is staffed. A fixed team with names for the first weeks, with daily coordination and clear prioritisation of tickets.
  • The first month-end close is planned. It is the real test of the system and needs support, not just go-live day.
  • Updates are part of operations. Business Central receives two major versions a year. Whoever documents customisations and tests updates in advance never has to set up an upgrade project again.

Where implementations fail most often

Rarely on a missing item on the list. Mostly because items were ticked off without anyone deciding: processes described but not agreed, data cleaned up but without a rule, tests done but without real cases. The checklist is therefore only as good as the steering behind it. Whoever assigns every open answer to a person and a date has the project under control before it gets expensive.

Basis: DGP project experience from Business Central implementations in the midmarket; time ranges and go-live criteria as on the linked knowledge pages.

Briefly asked

What belongs in a checklist for an ERP implementation?

Items from six phases: steering before the start, processes and requirements, system and partner, data and migration, testing and training, go-live and the weeks after. Every item needs a responsible person and a date.

How long does an ERP implementation take in the mid-market?

Close to the standard three to four months, in the most common midmarket case with legacy replacement six to nine, with several companies twelve and more. The conditions are in How long does a Business Central implementation really take?

Which item is most often underestimated in an ERP implementation?

The internal effort. Key users, data maintenance and testing cost time in your own company, and whoever releases nobody for it delays the project without noticing.

The order behind it: Best practices for a Business Central implementation

Related

Related questions

Time & cost

How long does a Business Central implementation really take?

8 to 16 weeks apply only to simple setups. Complexity determines the duration.

03.08.2026

Read →

In operation

Business Central go-live: how do I know whether we are ready?

Readiness is more than a green test report.

04.08.2026

Read →

Replacing a legacy ERP

Cleansing master data before an ERP migration: how to proceed?

Cleansing does not mean tidying up, it means deciding on the rules.

04.08.2026

Read →

Where does your project really stand?

At DGP you speak with an experienced consultant, not with a sales team.

Senior-led advisory conversation on Business Central and ERP at DGP

ERP implementation checklist: what has to be done in six phases before go-live

Around 30 items to tick off, from steering before the start to the first month-end close. From Business Central projects in the midmarket.

Frank Maier·Last updated: 19.11.2026

Contents
Your question in detail?

A senior-led conversation gets to the heart of your situation.

Before go-live, an ERP implementation needs answers in six phases: steering before the start (goal, decision-maker, budget including internal effort), processes and requirements (standard before customisation, interfaces, AI use cases), system and partner (demo on your own processes, names in the team, running costs), data and migration (master data measured, owners, two trial migrations), testing and training (real cases, roles, acceptance) and go-live and operations (go/no-go four to six weeks ahead, cutover rehearsal, support until the first month-end close).

How to use this checklist

The items follow the six phases of an implementation. Each item is worded so that it can be answered with yes or no. A no is not a drama, but an open decision with a name and a date. The only dangerous items are those where nobody knows who is supposed to answer.

Phase 1: Before the project starts

  • The goal is set in business terms. Not “a new ERP”, but what runs faster, safer or cheaper afterwards, such as the month-end close, delivery capability or order entry.
  • A decision-maker with time is named. Management sits on the steering committee, the internal project lead is released for a fixed share of time, not on the side.
  • The budget includes the internal effort. Key users, data maintenance, testing and training cost your own time. Whoever only counts licence and partner calculates too tightly.
  • Success criteria are measurable. How you will recognise in six months that the implementation was worth it is written down.
  • The escalation path is clear. Who decides when the department and the partner cannot agree, and by when.

Phase 2: Processes and requirements

  • The core processes are described, as-is and to-be. From quote to payment, from purchasing to warehouse, with the exceptions that really occur.
  • Standard before customisation is agreed. Every deviation from the standard needs a business reason, not a habit.
  • Requirements are prioritised. Must, should and could are separated, and every must has an owner in the department.
  • All interfaces are listed. Web shop, banks, EDI, warehouse management, time recording, payroll: with direction, frequency and owner.
  • The AI use cases are named. Two processes that cost the most manual work today, such as incoming invoices or orders from e-mails. What Business Central brings for this is described in Business Central agents and Copilot.

Phase 3: System and partner

  • The system was demonstrated on your processes. A demo following your script with your examples, not the standard vendor presentation.
  • You know the names in the project team. Who at the partner will actually consult and develop, and how much of that is senior experience.
  • The running costs are calculated. Licences per user, apps, support and further development. The list prices are in Business Central licence cost.
  • Cloud or on-premises is a deliberate decision. Copilot and the agents only exist in Business Central online. What that means for on-premises is described in AI for Business Central on-premises.
  • The contract governs changes. How new requirements are assessed, approved and invoiced, before the first one appears.

Phase 4: Data and migration

  • The master data is measured. Duplicates, empty mandatory fields and inactive records are counted before anyone cleans up. How to go about it is described in Cleansing master data before the ERP migration.
  • Every data area has an owner. Items, customers, suppliers, bills of materials, prices: one person from the department each, not IT.
  • It is decided what gets migrated. Open items and balances yes, the full history usually not. Access to the legacy system for audits and retention periods is settled.
  • At least two trial migrations are planned. The first shows the major errors, the second whether they are fixed.

Phase 5: Testing and training

  • The test cases come from real business transactions. Real orders, real special cases, real quantities, not invented examples.
  • End-to-end tests have run. From order to payment and from purchasing to posting, across all interfaces.
  • Roles and permissions are tested. Everyone only sees and posts what they should. That also applies to AI functions, because they work with the permissions of the user.
  • Key users are trained and train others. They know their area in the new system better than the partner and are the first point of contact on go-live day.
  • Acceptance is documented. Signed per process by the owner in the department, with a list of open items.

Phase 6: Go-live and the weeks after

  • Go/no-go criteria are written down. The decision is made four to six weeks before the date. How to recognise readiness is described in Business Central go-live: how do I know whether we are ready?
  • The cutover has been rehearsed. Sequence, responsibilities and fallback plan have been run through in a dress rehearsal.
  • Support after go-live is staffed. A fixed team with names for the first weeks, with daily coordination and clear prioritisation of tickets.
  • The first month-end close is planned. It is the real test of the system and needs support, not just go-live day.
  • Updates are part of operations. Business Central receives two major versions a year. Whoever documents customisations and tests updates in advance never has to set up an upgrade project again.

Where implementations fail most often

Rarely on a missing item on the list. Mostly because items were ticked off without anyone deciding: processes described but not agreed, data cleaned up but without a rule, tests done but without real cases. The checklist is therefore only as good as the steering behind it. Whoever assigns every open answer to a person and a date has the project under control before it gets expensive.

Basis: DGP project experience from Business Central implementations in the midmarket; time ranges and go-live criteria as on the linked knowledge pages.

Briefly asked

What belongs in a checklist for an ERP implementation?

Items from six phases: steering before the start, processes and requirements, system and partner, data and migration, testing and training, go-live and the weeks after. Every item needs a responsible person and a date.

How long does an ERP implementation take in the mid-market?

Close to the standard three to four months, in the most common midmarket case with legacy replacement six to nine, with several companies twelve and more. The conditions are in How long does a Business Central implementation really take?

Which item is most often underestimated in an ERP implementation?

The internal effort. Key users, data maintenance and testing cost time in your own company, and whoever releases nobody for it delays the project without noticing.

The order behind it: Best practices for a Business Central implementation

Related

Related questions

Time & cost

How long does a Business Central implementation really take?

8 to 16 weeks apply only to simple setups. Complexity determines the duration.

03.08.2026

Read →

In operation

Business Central go-live: how do I know whether we are ready?

Readiness is more than a green test report.

04.08.2026

Read →

Replacing a legacy ERP

Cleansing master data before an ERP migration: how to proceed?

Cleansing does not mean tidying up, it means deciding on the rules.

04.08.2026

Read →

Where does your project really stand?

At DGP you speak with an experienced consultant, not with a sales team.

Invitations by email

Stay on top of things without tracking everything yourself.

Once a month, Frank Maier puts into context what is moving in the ERP world. Plus the invitation to the next live webinar.

Thank you, you are signed up.