--- title: "The best upgrade options for Business Central 2025" id: "993719" type: "post" slug: "die-besten-upgrademoeglichkeiten-zu-business-central-2025" published_at: "2025-09-09T10:30:58+00:00" modified_at: "2025-09-12T12:06:23+00:00" url: "https://ioi.gmbh/2025/09/09/die-besten-upgrademoeglichkeiten-zu-business-central-2025/?lang=en" markdown_url: "https://ioi.gmbh/2025/09/09/die-besten-upgrademoeglichkeiten-zu-business-central-2025.md?lang=en" excerpt: "2025 is not a year for half measures. Since v26 (2025 Wave 1), there is a clear, step-by-step…" taxonomy_category: - "Business Central instructions & tutorials" --- # The best upgrade options for Business Central 2025 [https://www.facebook.com/sharer.php?text=The%20best%20upgrade%20options%20for%20Business%20Central%202025&u=https://ioi.gmbh/2025/09/09/die-besten-upgrademoeglichkeiten-zu-business-central-2025/?lang=en](https://www.facebook.com/sharer.php?text=The%20best%20upgrade%20options%20for%20Business%20Central%202025&u=https://ioi.gmbh/2025/09/09/die-besten-upgrademoeglichkeiten-zu-business-central-2025/?lang=en) [https://twitter.com/share?t=The%20best%20upgrade%20options%20for%20Business%20Central%202025&url=https://ioi.gmbh/2025/09/09/die-besten-upgrademoeglichkeiten-zu-business-central-2025/?lang=en](https://twitter.com/share?t=The%20best%20upgrade%20options%20for%20Business%20Central%202025&url=https://ioi.gmbh/2025/09/09/die-besten-upgrademoeglichkeiten-zu-business-central-2025/?lang=en) [http://www.reddit.com/submit?url=https://ioi.gmbh/2025/09/09/die-besten-upgrademoeglichkeiten-zu-business-central-2025/?lang=en](http://www.reddit.com/submit?url=https://ioi.gmbh/2025/09/09/die-besten-upgrademoeglichkeiten-zu-business-central-2025/?lang=en) [https://ioi.gmbh/2025/09/09/die-besten-upgrademoeglichkeiten-zu-business-central-2025/?lang=en](https://ioi.gmbh/2025/09/09/die-besten-upgrademoeglichkeiten-zu-business-central-2025/?lang=en) 2025 is not a year for half measures. Since v26 (2025 Wave 1), there is a clear, step-by-step path for many scenarios: For cloud migration, your on-prem solution must be upgraded to at least v25; in addition, v26 is a stepping-stone release, i.e. direct jumps across several major versions are restricted. This has a noticeable impact on budget, downtime and tool selection. ## You have these options when upgrading. ### 1) Greenfield / “Green meadow” Only important master data (debtors, creditors, articles, open balances if applicable) plus new processes/customizing in Business Central. **Advantages:**Lean, fast, less legacy. **Disadvantages:**History remains in the old system/archive; additional effort for reporting across old and new systems. ### 2) Complete data transfer Full history (master data and transaction data) moves to Business Central. **Advantages:**One system, complete information capability. **Disadvantages:**Technically more complex, higher data volume and therefore typically longer switching windows, more tests. ## The options at a glance | Option | Type / Approach | Suitable for | Parallel operation with Livesync | Go-live downtime (for technical reasons) | Remarks | | --- | --- | --- | --- | --- | --- | | Configuration packages (RapidStart) | Data transfer via Excel/Package; integrated in BC | “Greenfield” (master data, basic configuration) | No | Importing large amounts of data can block the system; not suitable for ongoing production | For initial setup; for mass imports better XMLports; BLOB/multi-line text via Base64 possible since 2024/25 | | DataMigrate Pro (IO Integrated) | Direct migration incl. bidirectional synchronization, delta loads | “Greenfield” and complete takeover | Yes – NAV & BC in parallel, live sync | Very low; switching time freely selectable | Supports very old NAV versions; target cloud or on-prem; no Jump versions required (provider information) | | Third-party provider (typically your Dynamics NAV & Navision partner) | Project service on Microsoft standard path (C/AL→AL, upgrade toolkit, data upgrade); clean start incl. data migration | Clean start or complete takeover | No (no live sync) | Yes – data upgrade requires maintenance window; one-way street | Test and productive data migration; custom tables optional | Note: Why “one-way street” for the standard path? During the Microsoft data upgrade, all clients are disconnected; after a successful data upgrade, replication from the old version is not permitted (risk of data corruption). This is for technical reasons and applies regardless of which service provider performs the upgrade. ## Strengths & weaknesses in detail ### Configuration packages (formerly “RapidStart”) **Pro:** - On board, cost-effective, fast for master data (customers, suppliers, articles, G/L basic configuration). - Since 2024/25: BLOB/multi-line text can be processed via package (Base64). **Contra:** - Not intended for existing productive companies; large imports may block use – for bulk imports XMLports. - No live sync, no history conversion (import only), testing/troubleshooting often manual. - No item transfer or posted / unposted documents (e.g. invoices) possible - Very slow with large amounts of data - Configuration packages must be imported in the correct order, otherwise there will be validation errors (for links between tables) Conclusion: Ideal for “greenfield sites”. Unsuitable or time-consuming and slow for complete data transfer (incl. posted items and receipts). ### DataMigrate Pro(IO Integrated) **Pro:** - Direct migration from very old Navision/NAV versions without “jump versions” - Bidirectional live synchronization (NAV↔BC), delta loads, parallel operation – resulting in minimal / no downtime and predictable cutover. - Cloud or on-prem target; suitable for greenfield (subset) and complete takeover. **Contra:** - Extensive features that mainly work via a command line tool. May require brief instruction in use. Conclusion: Technically attractive if downtime is to be minimized and the entire legacy history is to be transferred. ### Service provider on Microsoft standard path **Pro:** - Use of the standard upgrade path **Contra:** - Cutover downtime is inherent in the system: all connections are disconnected when data is upgraded; replication is no longer permitted afterwards – a one-way street. - For BC Online / SaaS, the OnPrem system must have at least v25 -> additional intermediate steps may be required. - Most expensive solution (usually between EUR 50,000 and 150,000) Conclusion: If a long downtime and high costs are not a problem, then this is an acceptable solution. ## Specifics that you should not ignore - Cloud migration only from v25 – An update to v25 is required before moving to the cloud; v26 acts as a stepping-stone release. - Data upgrade = maintenance window – regardless of the service provider, clients are disconnected until the step is completed; no provision is made for jumps back with renewed replication. A classic one-way street. This is no longer up to date! - Configuration packages are not mass ETL – For productive mass imports, Microsoft advises against packages (performance risk) and instead refers to XML ports. ## Decision matrix (short and sweet) | Goal / Framework | Recommendation | Reason | | --- | --- | --- | | Fast start, rethink processes, history in archive (“greenfield”) | Configuration packages for master data + new BC setup | Fast & cost-effective; not for mass imports in live operation | | Complete history, minimal downtime, very old NAV versions are supported | DataMigrate Pro | Direct migration with parallel operation & live sync; no jump versions (provider information) | | Fixed price, standard process, clear cutover possible | Dynamics NAV / Navision Partner | Standard upgrade with defined maintenance window | | BC Online mandatory & < v25 | DataMigrate Pro or first v25 via standard path, then cloud migration | Microsoft requires v25 before cloud migration; standard way = more steps/downtime | ## Risks & pitfalls that hurt - Downtime underestimated: With the standard upgrade, the data upgrade step is hard; if you have to plan to the minute, you need clean pre-tests or choose Livesync. - Data quality: Duplicates, incorrect number ranges, incorrect dimensions explode in the new system. Plan data cleansing at an early stage. - Add-ons/customizing: C/AL adaptations must be transferred cleanly to AL/extensions; the effort involved depends on the legacy scope. - Configuration packages overrated: Good for master data – not as history-capable ETL or for ongoing production. ## Checklist: How to make the right decision (in 30 minutes) - Does BC have to be online? If yes and you are < v25, calculate intermediate step v25 (the older the source version, the more intermediate steps are necessary) or check direct migration/live sync. - How much history do you need in BC? Master data only -> RapidStart; full history -> DataMigrate Pro or standard upgrade with go-live window and long downtimes. - Downtime tolerance: zero / hardly any tolerance -> live sync; weekend cutover and high costs ok -> standard upgrade. - NAV version very old? Direct migration without jump versions saves time/complexity. - Budget/responsibility model: technically driven & migration-focused -> DataMigrate Pro. | Provider / Tool | Source version | Next possible target version | | --- | --- | --- | | Microsoft / Standard upgrade | Microsoft Dynamics NAV 2009 / 5.0 | Microsoft Dynamics NAV 2013 R2 | | Microsoft / Standard upgrade | Microsoft Dynamics NAV 2013 R2 | Microsoft Dynamics NAV 2015 | | Microsoft / Standard upgrade | Microsoft Dynamics NAV 2015, 2016, 2017, 2018 | Business Central Spring 2019 (version 14) | | Microsoft / Standard upgrade | Business Central Spring 2019 (version 14) | Business Central 2024 release wave 2 (version 25) | | Microsoft / Standard upgrade | Business Central 2024 release wave 2 (version 25) | Business Central 2025 release wave 1 (version 26) | | IO Integrated / DataMigrate Pro | Any Dynamics NAV, Navision and Business Central version | Business Central Cloud or OnPremise (from version 21) | See also the [official documentation](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-paths) from Microsoft. ## Conclusion - Greenfield: Setting up new configuration packages for master data and processes. Fast, cost-effective – but not for mass imports in live operation. - Complete data transfer: If downtime is critical and costs need to be kept low or the source version is very old: [DataMigrate Pro](https://ioi.gmbh/datamigrate-pro/?lang=en) (parallel operation, live sync). - Classic cutover window acceptable and fixed price/standard important: Business Central Partner (like IO Integrated) – accept that data upgrade is a one-way street and costs can escalate. Add a comment ## Leave a Reply [Cancel reply](/2025/09/09/die-besten-upgrademoeglichkeiten-zu-business-central-2025/?lang=en#respond)