Step-by-Step A/B Migration: Safe Parallel Operation

Step-by-Step A/B Migration: Safe Parallel Operation of Sites

We faced a situation: a client lost 40% of traffic after fully switching to a new site due to unexpected bugs. To avoid such scenarios, we use A/B migration—the old and new sites run in parallel, traffic is switched gradually. This detects problems on a small audience before full transition. Our team, with certificates in web performance and over 10 years of experience, ensures stability at each step. Debugging savings can reach up to 70% compared to a full cutover. This approach provides business continuity: users don't notice the switch, and you maintain control (see A/B testing on Wikipedia).

How It Works: Architecture and Options

The basic scheme: DNS/CDN → Load Balancer (nginx/Cloudflare) → traffic distribution between old and new sites. Both systems must share data or synchronize in real time. Below are three common routing options.

Cookie-based routing is 1.5 times more stable for the user than Nginx weighted upstream, so it is often chosen for e-commerce sites.

Nginx Weighted Upstream

upstream site_upstream {
    server old-site:8080 weight=9;
    server new-site:8081 weight=1;  # 10% traffic
}

server {
    listen 80;
    server_name company.com;
    proxy_pass http://site_upstream;
}

Start simple: 10% → 25% → 50% → 90% → 100% with intervals of several days. Drawback: a user may switch between versions on repeat visits.

Cookie-Based Routing (Stable UX)

To keep a user on one version, use cookies:

split_clients "${remote_addr}${http_user_agent}" $new_site_user {
    10% "yes";
    *   "";
}

server {
    set $upstream_server "old-site:8080";

    if ($cookie_site_version = "new") {
        set $upstream_server "new-site:8081";
    }
    if ($new_site_user = "yes") {
        set $upstream_server "new-site:8081";
        add_header Set-Cookie "site_version=new; Path=/; Max-Age=86400; SameSite=Lax";
    }

    proxy_pass http://$upstream_server;
}

Cloudflare Workers

For even more flexibility we use Workers—code runs at the network edge. It checks cookies, hashes IP, and directs traffic without server load. Workers reduce latency by 2x on geographically distributed requests compared to nginx.

Why Data Synchronization Matters

If the old and new sites have different databases, data must be consistent. We use webhooks or queues (RabbitMQ, Redis Streams) to send changes in real time. For example, when a post is created on the old site, a request is sent to the new site with action and data fields. This prevents discrepancies in the catalog, orders, or user profiles. Data synchronization is the bedrock of a seamless migration; without it, business processes break and user trust erodes.

Metrics to Track During the Switch

We compare metrics side by side:

Alert: if new site error rate > 2x old site, auto rollback. Core Web Vitals (LCP, CLS, INP) are also a priority. Set up Grafana dashboards with thresholds for each metric.

Typical Pitfalls and How to Avoid Them

• No rollback plan: predefine triggers (error rate, conversion) and the procedure to switch back.
• Ignoring data sync: without it, users may see inconsistent data, losing trust.
• Ramping too fast: start with 5–10% and increase every 1–2 days after verifying stability.
• SEO duplication: set canonical URL to the old site until full switch to avoid duplicate content penalties.

Case Study: Electronics E-Commerce Store

A client wanted to migrate from Magento to Shopware. We configured cookie-based routing with 10% traffic to the new version. Conversion rose by 15%, error rate dropped from 1.2% to 0.4%. Full switch took two weeks—without sales loss. Debugging savings reached $12,000 compared to a full migration without A/B testing.

Step-by-Step Setup Guide

1. Audit current infrastructure—identify old and new site stacks, databases, integrations.
2. Choose routing method—based on session stability needs and complexity.
3. Configure load balancer—nginx or Workers.
4. Synchronize data—organize webhooks or queues for critical entities.
5. Monitoring and alerts—set up Grafana dashboards and thresholds.
6. Gradually increase traffic—every 1–2 days, increase share by 10–25%.
7. Full switch—after reaching 100% traffic and stable metrics.

What's Included in the Work

• Routing configuration (nginx/Cloudflare)
• Data synchronization setup
• Monitoring dashboards (Grafana, alerts)
• Rollback procedure documentation
• Client team training (2 hours)
• Post-migration support for 1 week
• Access to all configuration files and credentials

Guaranteed rollback in under 15 minutes if anything goes wrong.

Get a consultation on A/B migration setup before starting your project—it reduces risks. Contact us to discuss your project.

Estimated Timeline and Cost

Setup takes 4–7 business days depending on architecture. Cost ranges from $2000 to $5000, determined after an audit. Our certified engineers will help configure your migration—get a consultation today.

Order a project audit before migration—it saves weeks on debugging.

Website Redesign and Migration: CMS Change, SEO Preservation

A client came to us 6 weeks after a self-attempted redesign: 'We moved from WordPress to Tilda, traffic dropped by 70%.' I opened Google Search Console — 847 pages returned 404, the URL structure had completely changed, not a single 301 redirect was in place. Yandex hadn't reindexed the new site yet, positions collapsed. Recovery took 4 months and resulted in significant revenue loss for the quarter. Our experience — over 7 years and 80+ successful migrations, we guarantee position retention with the right approach.

Why Do Migrations Break SEO?

Search engines have indexed specific URLs. If /catalog/shoes/nike-air-max-270 turned into /products/nike-air-max-270 without a 301 redirect — all the link equity, traffic, and rankings go nowhere. Google says 301 passes ~99% of PageRank, but in practice positions recover over 2–8 weeks, not instantly.

Commonly, SEO gets broken not out of malice, but because a developer doesn't view the URL structure as a public API. Here are typical breakages:

How to Recover Traffic After a Failed Migration?

If traffic dropped, act immediately:

1. Crawl the new site for 404s and compare with the pre-migration URL list.
2. Create redirects for all lost pages with traffic >0.
3. Check structured data and meta tags on a test sample.
4. Daily monitor Coverage in Search Console and positions for top 50 queries.
5. If after 2 weeks traffic does not recover — deep audit of redirects (transitivity, chains, loops).

In our practice, a large e-commerce site lost 50% of traffic when moving from Bitrix to React + Strapi. We restored 95% of redirects in three days, and within 3 weeks traffic returned to 90% of original.

What Does a Pre-Migration Audit Include?

Before starting development on the new site:

1. Full crawl of current site via Screaming Frog or Sitebulb. Get list of all indexable URLs with traffic from Google Search Console.
2. Export all pages with organic traffic >0 over the last 6 months — these are priority for redirects.
3. Record all external backlinks to specific pages — Ahrefs, Semrush.
4. Snapshot current positions for key queries — baseline for post-migration comparison.
5. Save Core Web Vitals from Search Console for the previous 90 days.

Table for recording:

Contact us for a detailed pre-migration audit — we will help identify all risks and create an action plan.

URL Mapping and Redirects

For projects with 200+ pages, we create a mapping table: old URL → new URL → status (301, merged with another page, deleted). Each row is verified: does the content actually migrate here?

In Laravel, redirects are handled via configuration file and middleware, not .htaccess — faster and more manageable. For WordPress → Next.js: redirects are set in next.config.js (static) and at the Nginx/CDN level for dynamic ones. Old .htaccess on shared hosting with 500+ lines of redirects is a special hell. Each redirect is checked sequentially, performance suffers. We move to Nginx map directive or Redis cache for dynamic lookup. More at Wikipedia: HTTP 301.

How to Migrate Content from Different CMSs?

WordPress → Headless CMS (Contentful, Strapi, Sanity): WordPress REST API or WP All Export to export posts, meta fields, media files. Migration script in Node.js: parse export, transform structure, upload via CMS API. Media files are reuploaded to new storage, links updated in content. Typical problem — shortcodes in WordPress content ([gallery id="123"]): need parser and transformation to new format.

1C-Bitrix → modern stack: Bitrix stores content in non-standard tables with IBLOCK_ELEMENT_PROPERTY. Direct SQL export via phpMyAdmin or Bitrix API. Transformation is the longest part due to specific Bitrix data structure.

Heavy WYSIWYG → structured content: Years of editing in FCKEditor/TinyMCE leave inline styles, non-standard tags, broken attributes. HTML sanitize + transformation to Markdown or Portable Text (Sanity) with manual check of problematic pages.

How to Preserve Technical SEO Elements During Migration?

Structured data (Schema.org) — if the old site had Product, Article, BreadcrumbList markup, they must be on the new site too. Google Search Console → Enhancement reports will show loss of rich snippets.

Sitemap XML: generated automatically, submitted to GSC a day after launch. Old sitemap remains until full reindexing.

hreflang for multilingual sites: if tags are lost during migration, conflicts between language versions in search results will start within weeks.

Open Graph and Twitter Card meta tags — often forgotten when changing template, pages stop displaying correctly when shared on social networks.

Launch and First Weeks Monitoring

DNS propagation: DNS switching takes up to 48 hours, plan launch with buffer. Cloudflare as DNS provider — propagation takes minutes, not hours.

After launch, monitor daily: Search Console → Coverage (indexing errors), Analytics → organic traffic, year-over-year comparison, crawl site for 404 errors.

First 2 weeks are critical. If traffic drops more than 30% — immediate audit of redirects and comparison with pre-migration crawl.

What the Service Includes

Results you receive:

1. Migration plan with URL mapping and redirects in Excel/Google Sheets format.
2. Configured 301 redirects at server level (Nginx/Cloudflare/Vercel).
3. Migrated content with integrity check: images, meta fields, links.
4. Structured data (Schema.org) on the new site, identical to old or improved.
5. SEO report: position trend at 1, 3, and 6 weeks after launch.
6. Coverage monitoring in Search Console with error notifications.
7. Guaranteed position retention: if traffic drops more than 15% within the first month — free audit and correction.

Timelines and Estimates

• Redesign with migration for a small site (up to 100 pages): 4–8 weeks.
• E-commerce migration with 500+ product pages: 8–16 weeks.
• Only technical migration part (redirects, metadata) without redesign: 1–3 weeks.

Cost is calculated individually based on scope.

Get a consultation for your project — we will respond within a day. Order a pre-migration audit of your site and receive a detailed proposal with a redirect plan. Contact us to discuss details.