ERP implementation checklist: budget, migration and go-live

Define the business result and the first rollout

Choose the process that needs to improve and state a result the business can check. For example, an organisation might want the purchasing team to see approved orders and finance to reconcile the resulting liability without a separate spreadsheet. That is a hypothetical objective, not a measured result for any product. Name the companies, locations, transaction types and reporting needs in the first rollout. Keep later phases in a separate scope so every proposal prices the same starting point.

Price the people who will actually use the system

List the work done by full-time operators, occasional approvers, warehouse staff, managers, external accountants and administrators. Ask which licence or access arrangement supports each role in the proposed edition. A named user, a limited user and a read-only report recipient may have different rights. Write the required actions beside the quoted role rather than choosing the cheapest label. Include the users who will join during the rollout and the internal time needed for training and process ownership.

Keep software, implementation and operating costs separate

Request separate rows for subscriptions or licences, implementation services, data migration, integrations, training and recurring support. Record assumptions about company count, transaction volume, storage, environments and optional applications. Ask which activities are fixed in scope, which are estimates and what triggers an additional quote. The useful total is the cost of the retained operating arrangement. A starting subscription price does not define the full implementation, and a large project fee does not explain future renewal obligations.

Agree what will move from the old system

Create an inventory of master records, opening balances, open transactions, historical details and attachments. Assign an owner to clean duplicates and resolve missing references before the migration rehearsal. Define which information will move into the new system and which will remain in an accessible archive. For each migrated set, agree a count, total or other reconciliation that the process owner can review. Do not treat a completed import job as proof that the financial and operational records agree.

Give each integration an owner and an exception path

List every connected application, its source of truth, the direction of data movement and the expected timing. Then describe what happens when a message is duplicated, a required field is missing or the other system is unavailable. Include configuration, credentials, monitoring and the person who fixes rejected records in the scope. A connector appearing on a feature list does not establish the completed handover. Run one representative transaction through the entire path before accepting the integration.

Use representative acceptance tests with the right permissions

Build a small set of approved examples around the daily work and its exceptions. Include a normal transaction, a correction, an approval and the report used to reconcile the result. Test as the intended role rather than giving every participant unrestricted administrator access. Microsoft’s Dynamics implementation guidance includes testing, migrated-data validation and operational readiness in its go-live review. Use the requirements agreed for your own deployment; this guide does not claim a completed product trial or certify an implementation.

Make the launch decision concrete

Write the planned change window, final data preparation, verification tasks, owners and the criteria for proceeding. Decide who handles an unresolved issue and what the team will do if a required check fails. Prepare the support contacts and the workarounds that have actually been approved. Keep readiness separate from a date on a project chart. The business owner should be able to explain which processes and records were accepted, which limitations remain and who is responsible for the first operating period.

Keep the proposal and evaluation evidence together

Retain the scope, role map, dated quote, migration reconciliation, integration tests, training plan and support responsibilities. Compare NetSuite and Business Central, SAP and Oracle ERP or Sage Intacct and Acumatica around the relevant job. Use the software comparison scorecard to record your own assessed requirements, leaving unknowns unassessed.

Frequently asked questions