How can we help you?

What if migration was interrupted?

What if my Data Migration is Interrupted? Troubleshooting and Solutions

We strongly recommend running a demo data migration before initiating payments or a full live migration. This allows you to assess the migration performance using a limited number of items and identify any potential issues beforehand. If you encounter problems during the data migration process, our support team is ready to assist. Our technical engineers will investigate the issue and provide tailored solutions.

If the data migration does not work for you, please contact our support team. Our technical engineers will investigate the issue and provide you with relevant solutions.

Common Causes of Data Migration Interruption

Several factors can lead to interruptions during the data migration process. Here are some of the most common:

• Connection Issues: The connection to your source or target store might be interrupted or unavailable. Ensure stable network connectivity throughout the migration.
• Database Problems: Issues with your source or target database, such as downtime or errors, can halt the migration.
• Concurrent Migrations: Attempting to run two or more migrations simultaneously for the same stores can cause conflicts and interruptions. Only run one migration at a time per store pair.
• Bridge File Deletion: The Bridge.php file, crucial for establishing a connection between the stores, might be accidentally deleted during the migration. Ensure this file remains in place.
• Server Resources: Insufficient server resources (CPU, memory) on either the source or target server can cause timeouts and interruptions.
• Data Size and Complexity: Extremely large or complex datasets can strain the migration process, leading to errors or timeouts. Consider optimizing your data before migrating.

Preventing Data Migration Interruptions

To minimize the risk of interruptions during your data migration, consider these preventative measures:

• Stable Internet Connection: Ensure a reliable and stable internet connection for both your source and target stores.
• Database Health Check: Verify the health and stability of your source and target databases before starting the migration.
• Resource Allocation: Allocate sufficient server resources (CPU, memory) to both your source and target servers to handle the migration load.
• Scheduled Downtime: Schedule the migration during off-peak hours to minimize the impact on your stores and reduce the risk of server overload.
• Data Backup: Always create a full backup of both your source and target stores before initiating the data migration.

Next Steps

We strongly recommend to try the demo migration before implementing payments or live migrations. You will be able to check the data migration performance for a limited number of items. Start your free demo now!

If you continue to experience issues with your data migration, please don't hesitate to contact our support team for assistance. Contact support via Live chat or Schedule a Call with a Migration Expert.