A Shopware hosting migration is not complete when the files and database have been copied. The store also depends on complete commerce data, product media, runtime settings, background processing, cache state, and search visibility controls. Checking these areas before changing the domain helps prevent missing orders, broken checkout flows, unavailable images, and unexpected SEO changes.
Table of Contents
Why Shopware migration mistakes affect the storefront
Website migration means moving website files, databases and related services from one hosting environment to another. With careful planning, visitors can continue using the current server while the data is prepared on the new server, so the migration does not normally require downtime. Learn more about website availability during migration.
The main risk for an online store is not only that a page may fail to load. A transfer can also leave the new environment with incomplete business data or settings that do not match the old environment. The store may look correct while customers, orders, images, checkout or indexing behave differently.
Transfer the complete database, not only the catalogue
The database contains more than products and categories. Before switching traffic, compare the source and destination for customers, orders and payment-related records. Use the same reference point for both environments so the comparison covers the same migration state.
- Check that customer records are present and the total is consistent.
- Check recent orders, order statuses and payment-related information.
- Check products, variants, categories and prices that the storefront depends on.
- Repeat the comparison after the final data transfer if new orders or customer changes were made during the migration window.
An incomplete database transfer can make the new store appear operational while its business history is incomplete. Do not treat a successful homepage load as proof that the database transfer is complete.
Verify product media and storefront URLs
Product images and other media must be available from the new hosting environment. Check product pages, category pages and any other storefront areas that display images. Look for missing images, broken media links and incorrect paths rather than checking only a small number of products.
Review important URLs before DNS changes and again after the new environment receives traffic. Include product pages, category pages and other URLs that visitors and search engines use. A migration can preserve the site files while still leaving a URL or media path incorrectly connected to the new environment.
Check environment variables and background processing
Incorrect environment variables can prevent the application from using the intended database, services or runtime configuration. Compare the required runtime settings between the old and new environments, then test the storefront using the destination environment.
Background queues also need validation. Check that queued work is processed in the new environment and that it does not remain stuck. This matters for store activity that depends on background processing, including tasks connected with order handling, notifications or catalogue changes. A storefront test alone may not reveal a broken queue.
Clear and rebuild caches in the new environment
Cache data belongs to the hosting environment and can become stale after a migration. Old cache state may show outdated content or hide changes made on the destination server. Treat cache handling as a separate migration task.
- Complete the final transfer of the database, files and media.
- Prepare the destination environment with its current settings.
- Clear stale cache data on the destination.
- Rebuild or warm the cache through the normal store process.
- Open key storefront pages and confirm that the displayed content matches the destination data.
Check the store in a fresh browser session as well as the session used during testing. This helps separate current storefront behaviour from content that was already loaded before the migration.
Protect SEO settings during the move
A server move does not normally harm search engine ranking when the website is moved correctly. Read more about server moves and search engine ranking. The migration can still create visibility problems if important SEO settings are lost or changed.
- Check that important URLs still open on the destination environment.
- Check redirects for URLs that have changed.
- Check indexing controls before the public switch and after it.
- Check that the production store is not left with a staging or test indexing setting.
- Compare key SEO settings between the source and destination stores.
A staging environment can be used to test major changes without putting the current rankings at risk. See how staging supports safer SEO testing.
Run commerce tests before changing DNS
Before DNS changes, test the destination store as a customer would use it. Check product browsing, product images, cart actions and checkout behaviour. Include a test that covers payment processing and confirm that the resulting order appears correctly in the destination environment.
Also validate customer-related actions and the order status shown after checkout. The purpose is to confirm both sides of the transaction: the customer can complete the storefront flow, and the store records the resulting order and payment information as expected.
Use a three-stage migration check
| Stage | Checks to complete |
|---|---|
| Before DNS changes | Database records, customers, orders, payment information, media, URLs, redirects, indexing controls, environment variables, queues, caches and checkout. |
| During the final transfer | Transfer the latest database and files, then repeat checks for data that may have changed during preparation. |
| After DNS changes | Open key storefront pages, test checkout, confirm images and URLs, and check that the public store uses the intended indexing settings. |
DNS propagation typically takes a few hours, although it can take longer depending on the domain registrar and network conditions. Read more about expected migration availability. During this period, different visitors may reach different hosting environments, so keep the old environment available until the new destination is receiving traffic consistently.
When to pause the migration
Pause the public switch if customers, orders, payment information or media do not match the source store. Also pause if checkout fails, queues remain stuck, redirects are missing, or the destination still uses an unintended indexing setting. Resolve the affected area and repeat the relevant checks before directing the domain to the new hosting environment.