In B2B e-commerce, a platform change is rarely a purely technical decision. Anyone moving their existing shop to Shopware moves not just data but the entire accumulated visibility capital: every URL that ranks in the search results, every internal link, every snippet that buyers click. Google Search Central explicitly points out that with any significant change to a site you may experience ranking fluctuations while Google recrawls and reindexes the pages (Google Search Central). This fluctuation is normal and temporary, as long as the migration is planned cleanly. If it is not, a temporary dip can turn into a loss that drags on for months. This guide shows how a move to the Shopware Community Edition succeeds without giving away organic visibility: complete URL mapping, 301 redirects without redirect chains, clean data transfer and the byte-accurate preservation of titles, meta data and internal links.
Key takeaways
- Migrations do not lose rankings through the switch itself, but through missing or faulty redirects and changed on-page signals.
- Complete URL mapping of old to new addresses is the foundation: every indexed old URL needs a defined 301 target.
- 301 redirects preserve PageRank according to Google, but only without long redirect chains. Google recommends pointing straight to the final destination.
- Titles, meta descriptions, headings and internal linking should be carried over byte for byte so the relevance signals do not shift.
- After go-live, sitemap submission, change of address and close monitoring decide how quickly the rankings stabilize.
Why Migrations Can Cost Visibility
Organic visibility is an economic asset in B2B, not a soft marketing factor. In 2024 alone, around 140,000 digital commerce companies in Germany generated roughly 650 billion euros in revenue (Oxford Economics for bevh), a large part of it initiated through search. Anyone who loses rankings in a platform change loses not positions in a table but the initiation of real orders. That is exactly why the decisive question in any migration is not whether rankings move in the short term, but whether they fully recover afterwards.
Google describes the mechanism openly: in a move with changed URLs, the search engine first has to recrawl and reindex the new structure. As a rule of thumb, Google states that a medium-sized website can take a few weeks for most pages to move in the index, and larger sites take longer (Google Search Central). Fluctuations are to be expected in this window. It only becomes critical when the signals that carry a ranking are lost in the move instead of passing cleanly to the new address.
The most important of these signals is the redirect. According to Google, permanent 301 redirects do not cause a loss in PageRank (Google Search Central). If the redirect is missing, however, the old URL ends in a 404 error, and the authority built up over years evaporates. In project practice, most migration-related visibility losses trace back not to the new platform but to missing, wrong or chained redirects (project experience). How strongly the early, organic channel feeds the entire pipeline is also shown in the article on B2B visibility for business customers.
Temporary Is Not the Same as Permanent
URL Mapping: the Foundation of Every Migration
Before the first redirect comes the inventory. A complete URL mapping assigns every old, indexed address a unique new target. The basis for this is a consolidated list of all URLs in circulation: from a fresh crawl of the old site, from Search Console, from the existing XML sitemap, from the server logs and from the analytics data. Only the union of these sources reveals the true scope. Large B2B catalogs quickly generate a multiple of the pages visible in the navigation through filters, sortings and pagination.
- Consolidate all indexed URLs from crawl, sitemap, Search Console, server logs and analytics
- Assign every old URL a unique new target, one to one wherever possible
- Redirect pages without a direct counterpart to the closest matching category, not blanket to the homepage
- Explicitly account for parameter, filter and campaign URLs that carry real traffic
- Prioritize the mapping by traffic, rankings and revenue
- Keep the mapping as a versioned table and test it against the live URLs before go-live
Prioritize by Traffic and Rankings
One B2B peculiarity belongs in every mapping: the separation between publicly indexable information pages and the protected areas behind the login. Customer-specific prices, order history and framework agreements stay in the customer portal behind the sign-in and do not belong in the index, while category, product and guide pages should keep their rankings. Drawing this line cleanly helps decide which URLs need a 301 target and which deliberately do not.
301 Redirects Without Redirect Chains
Once the mapping is in place, the technical implementation follows as a 301 redirect. Two rules are decisive here. First, the permanent 301 instead of the temporary 302: only the 301 signals the final move and passes the link equity to the new target. Second, the direct path: every old URL should redirect to its final destination in a single step. Googlebot does follow up to 10 consecutive redirects in a chain (Google Search Central), but Google explicitly recommends pointing straight to the final destination and otherwise keeping the chain short, ideally to no more than three redirects (Google Search Central).
Straight to the Destination
Every old URL redirects to its final target in one step, not via intermediate stops. That preserves the link equity and saves crawl time.
301 Not 302
Permanent 301 redirects signal the final move. Temporary 302s keep the ranking on the old URL and dilute the signal.
Complete Coverage
Old filter, pagination and campaign URLs with traffic also need a target. Gaps end in 404 errors and lost rankings.
No Loops
Redirects must not point in a circle. A redirect loop makes the page unreachable for users and crawlers alike.
Check After Go-Live
A crawl of the new site reveals chains, loops and missing targets before they cost rankings.
Link Internally Direct
Internal links point to the new URLs, not to the redirected old ones. That way no internal click runs needlessly through a redirect.
Chains and Loops Are the Most Common Redirect Trap
Data Transfer: Products, Customers and Orders
In parallel to the URL level, the actual data moves into the new system. The Shopware Community Edition is open source under the permissive MIT license (Shopware) and is built on the PHP framework Symfony (Shopware). For the data transfer this means full control: products, categories, customers and orders can be imported in a structured way via the Admin API, and the open architecture makes it possible to map the field structures of the old platform cleanly onto the Shopware data model. Which B2B functions the CE brings natively is described in the article on Shopware open source for B2B sales.
| Data object | Challenge in the migration | Approach in Shopware |
|---|---|---|
| Products and categories | Divergent field structure, variants, units | Import via the Admin API, map attributes, model variants as properties |
| Customer accounts | Passwords, customer groups, price agreements | Carry over accounts, trigger a password reset, assign customer groups cleanly |
| Order history | References to old article numbers and statuses | Migrate or archive the history, retain documents in an audit-proof way |
| Media and documents | Data sheets, images, old file paths | Carry over assets and 301-redirect old paths to the new structure |
| Content and URLs | Ranking pages, internal links, snippets | Apply the URL mapping, carry over on-page byte for byte, set 301s |
| Prices and tiers | Customer-specific prices, quantity tiers | Sync from the ERP, use customer groups and the Rule Builder |
Critical for B2B operations are the connected systems. Customer-specific prices, stock levels and order data usually come from the ERP, product information from a PIM. Both connections have to be in place by go-live so the new shop shows correct prices and availability from the first minute. How these ERP interfaces and the PIM integration are planned is a work field of its own in the migration. For more depth: the article on ERP integration in B2B e-commerce and, for stock and lead times, the article on real-time availability in the B2B shop.
Keep the Fair Usage Policy in View
Preserving Titles, Meta and Internal Links Byte for Byte
The redirect brings users and crawlers to the new address. Whether the page keeps its ranking there is decided by the on-page signals. Page title, meta description, H1 and heading structure are an essential part of what makes a page relevant for a search query. If they are automatically regenerated in the move instead of carried over from the existing content, these signals shift, and even a technically clean redirect lands on a page that has changed in substance. The requirement is therefore: carry over the ranking elements byte for byte and change them only where an improvement is deliberately intended.
- Carry over page titles and meta descriptions per URL instead of letting them be regenerated automatically
- Keep the H1 and heading structure of the ranking pages
- Set canonical tags to the final new URLs, not to redirected addresses
- Switch internal links directly to the new target URLs (Google Search Central)
- Carry over structured data for products, breadcrumbs and FAQ
- Migrate images including alt text and descriptive file names
On-Page Signals Are Ranking Signals
Internal linking deserves special attention. Google recommends switching the internal links of the new site from the old to the new addresses using the URL mapping (Google Search Central). If internal references keep pointing to the old URLs, every click runs needlessly through a redirect, which binds crawl budget and worsens load time. Clean internal linking to the final targets is therefore part of the on-page preservation, not a later rework. How load time and indexability come together in Shopware is at the heart of our Shopware development.
The Migration Roadmap to Go-Live
A ranking-safe migration follows a clear sequence. It begins long before go-live with the inventory and ends not with the switch but with an observation phase. The following six steps summarize the flow, which we stagger in the guided implementation depending on the size of the shop, since Google explicitly notes that a site can also be moved in sections.
1. Inventory
Capture all URLs, rankings and content of the old site, from crawl, Search Console, sitemap, logs and analytics.
2. URL Mapping
Assign every old address a new target, prioritized by traffic, rankings and revenue.
3. Data Transfer
Import products, customers, orders and media into Shopware via the Admin API, connect ERP and PIM.
4. Build in Shopware
Recreate categories, templates and on-page signals, carry over titles and meta byte for byte.
5. Redirects
Generate the 301 map from the mapping, rule out chains and loops, switch internal links.
6. Go-Live and Monitoring
Submit the sitemap, set change of address, track crawl stats, 404 reports and rankings.
Most ranking losses in migrations are avoidable. They arise not from the new platform but from a patchy redirect logic and lost on-page signals, and both are a matter of preparation, not of chance.
After Go-Live: Monitoring and Safeguards
Go-live is the start of the most important phase, not its end. Immediately after the switch, a new XML sitemap should be submitted in Search Console so Google discovers the new URLs faster (Google Search Central). If the migration also changes the domain, the Change of Address tool belongs to it; for a pure move from HTTP to HTTPS, however, it is not needed (Google Search Central). In the days that follow, the crawl stats, the coverage report and the 404 messages show whether the mapping was complete or whether individual old URLs run into nothing.
- Submit the new XML sitemap in Search Console (Google Search Central)
- Use the Change of Address tool for a domain change (Google Search Central)
- Watch crawl stats, coverage and 404 reports daily in the first weeks
- Track rankings and organic traffic of the most important URLs against the baseline
- Keep 301 redirects active for at least one year (Google Search Central)
- Check server response times and Core Web Vitals of the new site
Do Not Switch Off Redirects Too Early
Safeguarding also includes the time after recovery. A stable migration is the basis for developing the new shop further instead of reworking mistakes. We secure load time and stability through ongoing performance optimization and a maintenance framework, described in more depth in the article on the performance of B2B shops. And because a move is a good occasion to put customer communication in order, it is worth looking at automated email flows in B2B, which cleanly accompany new accounts and orders after go-live.
Sources and Studies