Applies to Product - Dynamics 365 Business Central
What’s happening?
Customers are experiencing prolonged data migration times when transitioning from on-premises versions of Business Central to the cloud environment. Specifically, migrations that typically complete within a few hours are taking several days, leading to concerns about whether the process has stalled.
Potential Reason:
The delays in migration are attributed to various factors, including:
- The presence of extensions that may interfere with the data upgrade process.
- Insufficient resources allocated to the cloud environment during migration.
- Potential bottlenecks in the customer's infrastructure that could affect upload speeds.
Troubleshooting:
To address the migration issues, the following steps should be taken:
1. Monitor Migration Status: Regularly check the status of the migration process to determine if it is still running or has stalled.
2. Investigate Extensions: Identify any extensions that may be causing issues during the data upgrade. For example, one case indicated that an extension called TRIMIT was problematic.
3. Optimize Migration Process:
- Consider deploying the source database to Azure SQL Database to enhance data replication speed.
- Upscale the Azure SQL Database if high CPU and memory utilization is observed during migration.
- Reduce the number of companies being migrated to streamline the process.
- Skip the API data upgrade during the initial migration and run it after going live.
4. Collaborate with Infrastructure Team: Work with the customer's infrastructure team to ensure there are no bottlenecks affecting the upload process.
5. Trial Runs: Conduct trial migrations to Azure SQL first to assess the impact on migration times before proceeding to the full cloud migration.
For further details on optimizing cloud migration performance, refer to the relevant documentation provided by Microsoft.