Migrate from Microsoft Dynamics 365 Business Central

Move from Microsoft Dynamics 365 Business Central to PeakSpitz, safely.

Moving off Microsoft Dynamics 365 Business Central should feel like restoring from a backup, not a leap of faith. Your ERP / business suite data is read into a PeakSpitz environment of your own, checked against your real numbers, and run in parallel — while Microsoft Dynamics 365 Business Central keeps running, untouched, the whole time. Here is exactly how, step by step.

Microsoft Dynamics 365 Business Central is a full double-entry ERP with genuinely deep financials; its dimensional reporting and tight fit with Excel and the wider Microsoft stack are a real strength, and a partner can tailor it a long way. Teams usually move on for three reasons: the per-user Essentials or Premium licensing adds up as headcount grows, most changes route through a partner rather than your own staff, and for a small operation it is often more system than the day-to-day actually needs. PeakSpitz keeps the joined-up financials, real accounting with VAT, but ships sales, storefront, operations and inventory in one platform with unlimited users, and is usually live in about a week without consultants.

The safe way to leave Microsoft Dynamics 365 Business Central

Work down the list at your own pace. Nothing here is irreversible, and your current system stays live throughout.

  1. 1

    Before you touch anything — get a backup you own

    Get a copy of your data out of Microsoft Dynamics 365 Business Central that you control — a file held on your side, not just a setting inside the system. Confirm in your contract that you have the right to export, and note any renewal, notice or lock-in dates so the timing stays on your terms.

  2. 2

    Export your data

    Pull customers, products, open orders, history, invoices and ledgers out of Microsoft Dynamics 365 Business Central in the most complete format it offers — CSV, spreadsheet, or an account/API export. Take the history too, not just open items: past records, documents and contacts are worth keeping.

  3. 3

    Send us a sample

    Before you commit, send us a representative slice — a handful of customers, a few recent orders or bookings, part of your catalogue. We map it into PeakSpitz and show you the restored result, so you see exactly how your ERP / business suite data lands before you move the rest.

  4. 4

    See what maps to what

    We line Microsoft Dynamics 365 Business Central up against PeakSpitz: customers, products, open orders, history, invoices and ledgers become customers, catalogue, orders, documents and ledgers in one joined-up system. Anything without an obvious home is flagged early, not discovered late.

  5. 5

    Bring it in — a read-only restore

    Your data is read into a fresh, isolated PeakSpitz environment of your own. Nothing inside Microsoft Dynamics 365 Business Central is touched, changed or switched off — it keeps running exactly as it is.

  6. 6

    Verify against your numbers

    Before you trust it, reconcile the totals — balances, counts, tax and revenue — against what Microsoft Dynamics 365 Business Central shows today. The numbers have to match before anything goes live.

  7. 7

    Run both in parallel

    Keep Microsoft Dynamics 365 Business Central live and run PeakSpitz alongside it for as long as you like. Compare like for like, move one area across first, and build trust before you depend on it. No big-bang cutover, and no deadline from us.

  8. 8

    Cross over and decommission — on your terms

    Switch over only when PeakSpitz has earned it. Keep your Microsoft Dynamics 365 Business Central export archived as a safety net, and close the old subscription when you are ready — not a moment before.

What maps where: Microsoft Dynamics 365 Business Central → PeakSpitz

Microsoft Dynamics 365 Business Central

Customers

PeakSpitz

Customers

Microsoft Dynamics 365 Business Central

Vendors

PeakSpitz

Suppliers

Microsoft Dynamics 365 Business Central

Items (item cards)

PeakSpitz

Products / inventory items

Posting groups and number series are reconfigured in PeakSpitz, not imported.

Microsoft Dynamics 365 Business Central

Sales Orders

PeakSpitz

Sales orders

Open orders come across; posted sales invoices are typically kept read-only rather than replayed.

Microsoft Dynamics 365 Business Central

Financial Dimensions (Department, Project, and similar)

PeakSpitz

Reporting categories on transactions

Which dimensions survive is a deliberate mapping decision, not a straight lift-and-shift.

Microsoft Dynamics 365 Business Central

Copilot (advises in-product)

PeakSpitz

Spitz, the in-product AI that acts the moment you approve

What to watch when leaving Microsoft Dynamics 365 Business Central

  • AL extensions and any AppSource add-ons do not transfer as code. They are re-expressed as configuration or as integrations over the open REST API and webhooks.

  • Much of a Business Central setup commonly lives in configuration a partner made, such as number series, posting groups, dimension defaults and ISV add-ons. Inventory what your partner configured before cutover, since it is not all visible at a glance.

  • Posted documents and G/L entries are typically kept as read-only history rather than migrated entry-by-entry. Bring open balances and open orders, and export the closed history for archive.

  • Power Automate flows and Copilot prompts built around the Microsoft stack are tied to it. Re-plan the automations you rely on around Spitz and the REST API rather than expecting them to carry over.

Common questions about leaving Microsoft Dynamics 365 Business Central

Will we still need a Microsoft partner to make changes?

Business Central's partner network is a genuine strength for complex, tailored rollouts. PeakSpitz is built to be configured by your own team and is usually live in about a week without consultants, with the open REST API and webhooks reserved for the genuinely custom work.

We pay per user for Essentials or Premium — how does PeakSpitz price?

PeakSpitz includes unlimited users on every plan, so adding staff or giving the warehouse and shop floor access does not change the bill. That removes the per-seat and Essentials-versus-Premium math entirely.

What happens to our financial dimensions and reporting?

Dimensions are an analytical tagging layer, and the ones you actively report on carry over as categories on transactions. Deciding which to keep is worth doing deliberately at cutover rather than importing every historical tag.

As much help as you want

Do it yourself, or have us map your fields, run the import and reconcile the result with you. Support is a ladder — you start where you are comfortable and step up only where an area needs it.

See the full safe-migration approach →

Why people leave Microsoft Dynamics 365 Business Central

PeakSpitz runs the whole business on one AI platform — not a single corner with the rest bolted on — with Spitz AI and unlimited users included. See the difference side by side.

Compare PeakSpitz vs Microsoft Dynamics 365 Business Central →

Bring your Microsoft Dynamics 365 Business Central data in safely. Cross over when you are ready.

Send us a sample of your data and we will show you the restored result — no commitment, no risk to your live system.