An implementation checklist for Business Central you can tick off

Decisions to make before kickoff

Start with ownership. Name an executive sponsor and a project lead with time set aside. Add one process owner each for finance, sales, purchasing and operations. Then write down the scope in plain sentences. Say which companies, which locations and which processes are in the first phase. Also say which are left for later.

Then settle the commercial and technical basics. Choose Essentials or Premium. Count full users, Team Members and Device licenses. Confirm the Microsoft 365 tenant that will hold the environment. Decide the target cutover point around your financial calendar. Finally, list every system that must exchange data with Business Central.

Setup steps on a Business Central implementation checklist

Create the production and sandbox environments in the admin center, then the company. Work through Assisted Setup for company information, the accounting periods and sales tax. Build the chart of accounts, dimensions, posting groups, number series, payment terms and bank accounts. Record each decision in a short setup document.

Next come the operational areas. Set up locations and, if you use them, bins and warehouse documents. Define item categories, units of measure, costing methods and item tracking codes. Configure Sales and Receivables Setup, Purchases and Payables Setup and Inventory Setup. For Premium, add Manufacturing Setup. Add approval workflows and email accounts last.

Data migration on the Business Central implementation checklist

Agree which data moves and which stays behind. Master data normally includes customers, vendors, items, the chart of accounts, bills of materials and fixed assets. Transaction data is usually limited to a few sets. Those are open sales and purchase orders, open receivables and payables, inventory on hand and the opening trial balance.

Clean the source data before loading it. Remove duplicates, close dead records and fix addresses and tax details. Then load with configuration packages and journals in the sandbox. Reconcile totals back to the old system, and have the process owners sign off. Repeat the load at least once as a timed rehearsal before cutover.

Testing and training checklist

Write test scripts from real work, not from menus. Each script follows a process from start to end, such as quote to cash or purchase to payment. It also includes the awkward cases. Those are returns, partial shipments, credit memos and prepayments. Process owners run the scripts in the sandbox with migrated data and log every issue.

Train people on their own role with the same scripts. Set up role centers and permission sets for each job. Have users sign in as themselves, so security is tested too. Print and check every outgoing document, including invoices, statements, purchase orders and checks. Also test each integration with realistic volumes.

Cutover items on the Business Central implementation checklist

Prepare a cutover plan that lists each task, its owner and its order. Freeze the old system, extract final data, load and reconcile. Then post opening balances, turn on integrations and job queue entries, and release users. Agree in advance what would cause a postponement. Also agree who makes that call.

Plan the first weeks as carefully as the cutover. Decide how users raise questions and who answers them. Pick a date when you will walk through the first month-end close together. Our consultants can run the whole project. They can also step in for single stages, such as data migration or testing.

Questions about the Business Central implementation checklist

Who should own the checklist inside our company?

The internal project lead should own it. That person does not need to be technical. But they do need the authority to chase decisions, and enough time away from daily duties. The partner keeps a project plan, and the checklist stays with the customer. So nothing depends on one side's memory, and every open item has a named owner.

Which checklist items are skipped most often?

Document layouts, permissions and rehearsal loads. Teams focus on setup and leave invoice formats and security until the last moment. Then they find problems on the first live day. Testing with real users who sign in as themselves catches most of these in good time. So add a line for each of the three to your Business Central implementation checklist.

Does every item apply to a small company?

The stages apply to everyone, and only the depth varies. A small distributor may skip bins, manufacturing and intercompany setup entirely. It still needs a clear scope, clean data, tested documents and trained users. Cutting those is what turns a small project into a difficult one. So shorten the list, but do not drop the stages.

How do we track integrations on the checklist?

Give each integration its own line. Note the owner, the direction of data and the method, such as an API, a connector or a file. Add a test result. Include the bank, payroll, the web store, shipping carriers and any reporting tool that reads Business Central data. Then go over the lines at each steering meeting, until all of them pass.

Can the checklist be used for a second phase?

Yes. Later phases, such as adding warehousing, manufacturing or another company, follow the same stages on a smaller scale. You decide, set up, load, test and cut over. Keeping the first checklist makes it easier to see what you deferred and why. So treat the first version as a template, and copy it for each new phase. Each phase then has its own Business Central implementation checklist.

Related pages for your Business Central implementation checklist

The Business Central implementation checklist tells you what to do. These pages explain how. They include the full implementation guide and the go-live checklist for cutover day. They also describe how our consultants deliver implementation and data migration work. Read the implementation guide first, then return here and tick off each stage with your project team. For the product detail, see Business Central documentation on Microsoft Learn.