# Business Central Go-Live Cutover Plan Template

> Source: https://netray.co/tools/business-central-go-live-cutover-plan-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A cutover runbook for moving to Business Central: freeze, extract, load, reconcile, go/no-go decision, hypercare and rollback.

## Category

microsoft-dynamics

## Erp

Microsoft Dynamics 365 Business Central

## Audience

- BC project manager
- Cutover lead
- Finance controller

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Customer

**Key:** customer

**Type:** text

**Default:** Northfield Precision Ltd

#### Cutover start

**Key:** cutover_date

**Type:** date

**Default:** 2027-03-26

#### First business day live

**Key:** golive_date

**Type:** date

**Default:** 2027-03-29

#### Legacy system

**Key:** legacy

**Type:** text

**Default:** Dynamics NAV 2016

#### Cutover lead

**Key:** lead

**Type:** text

**Default:** P. Okafor

#### Freeze rules

**Key:** freeze

**Type:** textarea

**Default:** No new master data after Friday 14:00. Open transactions are posted or cancelled before 17:00. Legacy set to read only after the final backup.

#### Rollback trigger

**Key:** rollback

**Type:** textarea

**Default:** Rollback if the trial balance does not reconcile to zero variance or inventory value differs from legacy by more than the agreed tolerance by Sunday 18:00.

**Blocks:**

#### Cutover Plan: {{customer}}

**Body:** Legacy system: {{legacy}}
Cutover lead: {{lead}}
Cutover start: {{cutover_date}}
Live from: {{golive_date}}

#### 1. Freeze rules

**Body:** {{freeze}}

#### 2. Cutover timeline

**Table:**

**Columns:**

- Time
- Task
- Owner
- Duration
- Status

**Rows:**

**0:** Fri 17:00

**1:** Final legacy backup and freeze confirmed

**2:** IT

**3:** 1h

**0:** Fri 18:00

**1:** Extract master data and open balances

**2:** Data lead

**3:** 3h

**0:** Fri 22:00

**1:** Load master data through configuration packages

**2:** Consultant

**3:** 4h

**0:** Sat 08:00

**1:** Load opening balances and open documents

**2:** Finance

**3:** 4h

**0:** Sat 14:00

**1:** Reconcile G/L, customers, vendors, inventory

**2:** Controller

**3:** 6h

**0:** Sun 10:00

**1:** Smoke tests and permission checks

**2:** Key users

**3:** 3h

**0:** Sun 16:00

**1:** Go/no-go meeting

**2:** Steering group

**3:** 1h

#### 3. Reconciliation checkpoints

**Table:**

**Columns:**

- Area
- Legacy figure
- BC figure
- Variance
- Accepted by

**Rows:**

**0:** G/L trial balance

**0:** Customer ledger

**0:** Vendor ledger

**0:** Inventory value

**0:** Fixed assets

#### 4. Go/no-go criteria

**Body:** All reconciliation variances within tolerance. Smoke tests passed for sales, purchasing, inventory and finance. Users have correct roles and permission sets. Support rota confirmed for hypercare.

#### 5. Rollback plan

**Body:** {{rollback}}

#### 6. Hypercare

**Body:** Daily stand-up for the first two weeks, a defect triage queue with named owners, daily posting checks and a first month-end close review.

#### Approvals

**Signatures:**

- Project manager
- Finance controller
- Business sponsor

**Notes:** Times, owners and tolerances are examples. Rehearse the full timeline at least once with real volumes, and record actual durations to adjust the plan.

## Content

**Intro:** A go-live succeeds on a rehearsed plan, not on heroics. This template gives you a cutover runbook with freeze rules, an hour-by-hour timeline, reconciliation checkpoints, go/no-go criteria and a rollback trigger for Business Central.

**Sections:**

#### How to use it

**Body:** Enter the dates, legacy system and cutover lead, then write the freeze and rollback rules in your own words. Export the document and edit the timeline for your actual sequence. Share it with every task owner, then rehearse it on a copy of production data. After each rehearsal, update durations and fix the slowest or riskiest steps.

#### The core sequence

**Body:** A typical Business Central cutover freezes the legacy system, extracts final master data and balances, loads master data first, then opening balances and open documents, then reconciles every area before users are allowed in. Load order matters: setup and dimensions, then accounts, customers, vendors, items, then open sales and purchase documents, inventory by location and finally journals for balances.

**Bullets:**

- Rehearse at least twice with production volumes
- Post opening balances in the correct period and posting date
- Switch off integrations that should not run during the load

#### Go/no-go and rollback

**Body:** Set criteria in advance, with numeric tolerances for reconciliation, so the decision is not emotional at 4 pm on Sunday. A rollback plan means the legacy system can be reopened with no data loss, and that you know the last point at which that is still true. After users post in Business Central, rollback becomes much harder, so the decision point must precede first postings.

#### Common mistakes

**Body:** Under-estimating load and reconciliation time is the top cause of failed cutovers. Others include forgetting number series starting values, leaving test data in the tenant, missing permission sets for key users and failing to tell customers and suppliers about changed document formats or bank details.

**Cta:** Netray can build scripted reconciliation checks between the legacy ERP and Business Central so variances are found in minutes. Ask for help with cutover tooling.

**Faq:**

#### How long should a Business Central cutover take?

**Answer:** For small and mid-size companies it is often a weekend, but volume and complexity matter. Inventory, open orders and fixed assets take the longest. Rehearsals tell you the real duration; use the slowest rehearsal plus a buffer.

#### Should we migrate historical transactions?

**Answer:** Most projects load balances and open items only, and keep history in the old system or a reporting archive. Loading full history raises cost and reconciliation effort. Decide based on legal retention and reporting needs.

#### What belongs in hypercare?

**Answer:** Fast defect triage, extra on-site or remote support for key users, daily checks of postings and integrations, and the first period close. Define exit criteria, such as no open high defects for a week, rather than a fixed date alone.

#### Can this be used for a NAV to Business Central upgrade?

**Answer:** Yes, with changes. Upgrades focus on data upgrade runs, extension deployment and user switchover rather than cold loads. Keep freeze, reconciliation, go/no-go and rollback sections, and replace the load tasks with your upgrade steps.

## Search terms

business central go live checklist, business central cutover plan template, erp cutover plan template, dynamics 365 business central go live plan, erp go live runbook template, business central cutover weekend

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json