Business Central· Cutover
OverviewMCP server
Pre-implementation
  1. Implementation plan
  2. Discovery
  3. Data assessment
  4. Solution design
Implementation
  1. Configuration
  2. Data mapping
  3. Data migration
  4. Testing and UAT
  5. Cutover
Post go-live
  1. Hypercare
  2. Handover
Step 9 of 11 · Implementation · Updated October 26, 2026

Business Central cutover and go-live

Cutover is the planned move from the legacy system to Business Central: the freeze, the final loads, the opening balances and the go/no-go call. superglue's agent writes the runbook from the project and the rehearsal, runs the final and delta loads with the tested tools, and reconciles before you and the client make the call.

Start a Business Central projectTalk to us

How this step works

What the agent does

  • Writes the cutover runbook with tasks, owners and timings from the rehearsal.
  • Runs the final and delta loads with the tools tested in the rehearsal.
  • Reconciles opening balances and open items against the legacy system.
  • Prepares the go/no-go summary with the open issues.

What you decide and approve

  • The cutover date and the freeze window.
  • Go or no-go, together with the client.
  • The fallback plan if the answer is no.

What the client gets

  • A cutover runbook.
  • A signed go-live reconciliation.

What makes a Business Central cutover work

  1. 01

    Plan the freeze and the sequence

    Agree the final extraction window, the transaction freeze, the load order and the reconciliation after cutover. Write each step into the runbook with an owner and a time.

  2. 02

    Restrict posting dates during the load

    Set Allow Posting From and Allow Posting To in General Ledger Setup and User Setup. Nothing then posts outside the opening balance period by mistake.

  3. 03

    Know how to roll back

    Record the time before the final load. An admin can restore the environment to a point in time from the admin center if the go/no-go decision is no.

  4. 04

    Turn on job queues and integrations last

    Start job queue entries, workflows and integrations only after the final load reconciles. Watch the first invoice run, payment run and bank reconciliation with the key users.

Frequently asked questions

What makes a Business Central cutover go well?

Plan the freeze and the sequence; Restrict posting dates during the load; Know how to roll back; Turn on job queues and integrations last. The agent runs the final loads with the tools tested in the rehearsal.

Who makes the go-live call?

You and the client do. The agent prepares the reconciliation and the list of open issues for the go/no-go meeting.

How does superglue work with our consultants?

superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.

Can we use our own implementation method?

Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.

Which systems can we migrate from into Business Central?

Common sources are Microsoft Dynamics GP, Dynamics NAV, QuickBooks, Sage 50 and spreadsheets. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.

Is client data safe?

superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.

How do we start?

Start with one live Business Central project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.