Business Central Implementation Checklist: 12 Go-Live Decisions

• Define and approve what “done” means.
• Reconcile clean data before the final migration.
• Test complete workflows, exceptions and real transaction volumes.
• Assign support and internal ownership before go-live.

A Business Central implementation checklist should confirm that the company is operationally ready, not merely that the software has been configured. Most ERP go-lives struggle because important decisions remain unresolved until the final week, when the team has little time to make them properly.

1. Does everybody agree on what “done” means?

Write down the main requirements from the project charter and ask end-users to approve them. A shared definition of completion gives the team something more specific than the go-live date against which to assess readiness.

This checklist does not replace a detailed project plan. It exposes uncomfortable questions while they are still relatively inexpensive to answer. If go-live is the only milestone the team can name, the project may appear finished before users, processes and controls are genuinely ready.

The Business Central implementation checklist requires both clean source data and reconciled opening balances. Importing records successfully is not enough when the records contain duplicates, obsolete entries or inconsistent names.

2. Has the data been cleaned, not only imported?

Review customers, vendors and items before the final migration. Duplicate customers, inactive items and vendors recorded under three spellings will not improve simply because they have moved into Business Central. Assign responsibility for cleansing the data and identify the person who will sign off on the result.

3. Are opening balances reconciled?

Customer, vendor, bank, inventory and general ledger balances should match the legacy system. The person responsible for closing the books should confirm that reconciliation rather than leaving approval only to the consultant. This provides an operational and accounting check on the numbers that will form the starting point in the new system.

A company proves cutover readiness by running at least one mock go-live and testing complete business scenarios from beginning to end. The first migration should never take place on the day when its timing and outcome matter most.

4. Have you run a mock go-live?

Use a sandbox and complete at least one mock go-live. The exercise shows how long the real cutover may take and reveals which steps or components break. Record what happens so the team can adjust responsibilities and sequencing before the live migration.

5. Did users test complete scenarios?

Creating a sales order alone is not a complete test. Users should create the order, reserve stock, ship it, invoice it, receive payment and check the resulting accounting. Testing the entire sequence reveals gaps that an isolated screen or transaction may not expose.

The Business Central implementation checklist should verify role-based permissions, Canadian tax and currency scenarios, and integrations operating at realistic volume. These areas require deliberate tests because a simple configuration review may not show how they behave in routine work.

6. Are permissions set by role?

Decide who can release orders, post journals, change prices or delete documents. Configure access according to those responsibilities instead of granting broad permissions to everybody because doing so is faster during implementation. The decisions should reflect how each role is expected to work after go-live.

7. Are Canadian tax and currency setups verified?

Test GST/HST, provincial taxes and CAD/USD transactions with real examples. Include straightforward transactions as well as a few awkward cases. The objective is to verify that the setup handles the transactions Canadian finance and operations teams expect to process.

8. Are integrations tested with real volume?

An online store, point-of-sale system or bank feed may work with ten test records but behave differently during a normal Monday morning of orders. Test integrations with a representative operating volume rather than assuming that a small successful sample proves readiness.

Users should be prepared to resolve common exceptions, know where to ask questions and have an internal owner who can explain expected system behaviour. A menu tour alone does not create operational readiness.

9. Do users know what to do when something goes wrong?

Training should cover exceptions such as an incorrect quantity, a cancelled order or a missing vendor. Users often remember these unusual situations long after they forget a general tour of the menus. Scenario-based training gives them a practical response when a transaction does not follow the ideal path.

10. Who answers questions after go-live?

Name the people who will answer questions, the channel employees should use and the expected response. “We will figure it out” is not a support plan. Clear arrangements help users know where to take problems during the period immediately after launch.

11. Is there an owner inside the company?

Someone within the company should understand how Business Central is supposed to work and be able to make small decisions without waiting for a consultant. This internal owner provides continuity between finance, operations, management and external support.

The first month-end should be planned before go-live because it is the first full examination of the new system’s accounting processes. Waiting until the close begins leaves little room to clarify responsibilities, reporting needs or issue handling.

12. Is there a plan for the first month-end?

Agree on who will complete each task, which reports the company needs and how the team will manage issues. Include the people who normally close the books, since they must work with the results and confirm that the process supports their responsibilities.

The month-end plan should be treated as part of implementation readiness rather than as a later finance task. It connects migrated balances, complete transaction testing, user knowledge and support arrangements in one practical operating cycle.

Your next step is to review the Business Central implementation checklist with finance, operations and management in the same room. Work through all 12 decisions and pay attention when a question produces a long silence; that is usually the item to address first.

Document the answer, owner and required follow-up for each unresolved point. Do not treat agreement as complete until the relevant end-users and business owners have participated. If a Business Central project is approaching go-live and the team wants a second opinion, GEM365 can review the readiness questions with the company.