SERVICE · SEO-FIRST MIGRATIONS FOR MID-MARKET

Store migration without losing Google rankings and without sales downtime.

We specialize in migrations of stores generating €1–10M in annual revenue, where a failed migration means hundreds of thousands of euros in monthly losses. We run every project SEO-first from the first sprint, with contractual guarantees — the average organic traffic drop in our migrations is under 3% against an industry benchmark of 15–30%.

Free migration audit → See migration case studies →

≤ 3%

Maximum organic traffic drop

0 days

Sales downtime

100%

URL mapping validated by SEO

01 Migration scenarios

Three migration paths we lead mid-market stores down most often.

Each of the scenarios below has a fixed-price offer following a free technical audit. The choice of path depends on catalog scale, traffic profile, expansion plans and the client team's internal capabilities.

For stores that have outgrown PrestaShop.

PrestaShop → Sylius headless

The most frequently chosen path for mid-market B2C and B2B with a 5–50k SKU catalog. Headless architecture provides full frontend flexibility (Next.js, Nuxt) with a custom backend on Sylius.

PLN 150-250k

14-22 weeks

For brands with European expansion plans.

PrestaShop → Shopify Plus

Stable infrastructure, fast implementation, ready-made EU marketplace integrations. The choice for D2C brands planning to scale beyond €6M in revenue with simultaneous presence in multiple markets.

PLN 100-180k

8-14 weeks

For stores on custom legacy code from five years back.

Legacy PHP → Symfony

The most challenging scenario — rewriting a store from PHP 5.x to modern Symfony while preserving full business logic, SEO indexes and historical URLs. Three to twelve years of custom code reconstructed with documentation.

PLN 250-450k

22-40 weeks

02 Methodology · SEO-first

Five steps that secure your organic traffic.

Most agencies run migrations technically first and treat SEO as a remediation layer after launch. We reverse that order — every sprint starts with an SEO decision, only then a technical one. That's why our average traffic drop is under 3%.

Technical audit and SEO baseline

Week 1-2

A full technical audit of the current store (URL structure, indexable pages, internal linking, schema markup, Core Web Vitals) plus an organic traffic baseline from Google Search Console and Ahrefs. This produces a "what we absolutely preserve" document — a list of the 200-500 most important URLs by traffic and conversions.

Information architecture and URL mapping

Week 2-4

We design the new store's structure with one-to-one URL mapping for every indexed page. Every URL is validated by an SEO specialist, not just a developer. This produces a redirect map that's imported into regression tests before launch.

Development in two-week sprints

Week 4–18 · depending on scale

Iterative development with continuous staging validation. After every sprint: automated SEO tests (mapping correctness, schema markup, Core Web Vitals, indexability) plus manual review by an SEO specialist. The client has access to the Gorilla Panel with transparent hour tracking.

Cutover without sales downtime

Week 18–19 · weekend launch

Production migration during a low-traffic window (typically Sunday night). A full rollback plan in case of critical issues. 24/7 monitoring for the first 72 hours by an on-call DevOps engineer. Zero-downtime cutover — customers can keep buying throughout the process.

90-day post-launch monitoring

Week 19–32 · included in the project

90 days of post-launch monitoring included in the migration price — weekly organic traffic reports, 404 monitoring, new-page indexation verification, Core Web Vitals regression alerts. If we see a drop above 5% in the first 30 days, we fix it at no extra cost.

04 Transparency · What's included

We show what you get and what's NOT included in the migration price.

The worst thing for a mid-market client is finding out after signing the contract that "that wasn't in scope." Below is full transparency — on our side full scope of responsibility, on the other clear boundaries where additional work requires additional arrangements.

✓

What you get for the migration price

Full technical and SEO audit of the current store with organic traffic and conversion baseline
One-to-one URL mapping of all indexed pages, validated by an SEO specialist
Implementation of the new store on the chosen technology (Sylius, Shopify Plus, Symfony)
Product catalog migration from the current store including attributes, categories and media
Historical order and customer migration with anonymization of sensitive data
Production cutover without downtime over the weekend, with full 72-hour monitoring
90-day post-launch monitoring included — weekly SEO reports, regression alerts, drop remediation
Technical documentation of the new store for the client's internal IT team
Training for the client's team on the new platform (4–8 hours of online workshops)

What requires additional arrangements

Shopify Plus, Sylius Enterprise or other commercial platform licenses — paid directly to the vendor
Hosting and production infrastructure — can be taken from us (Growth Retainer) or from an external provider
Integrations with external systems (ERP, WMS, marketplace) — quoted individually based on API and scope
Custom functionality beyond the platform standard (e.g. dedicated product configurator) — separate project module
Blog and marketing content migration outside the catalog — optional add-on service
Content translation into foreign languages — external provider or client's in-house translators
Ongoing care after 90 days — we move to SLA (from €220/mo) or Growth Retainer (from €2,800/mo)

03 Hero migrations · Social proof

Two migrations that best show how we work.

We chose these two cases not because they're the largest — but because they show two fundamentally different migration stories: one from legacy custom code, the other from a popular SaaS to an enterprise platform.

Bogart Furniture

LEGACY PHP → SYMFONY FURNITURE B2C 12 YEARS LEGACY

Migration after twelve years of custom development without losing rankings.

A furniture store with twelve years of custom code on PHP 5.4. Full rebuild of business logic on modern Symfony 6 with preservation of all indexed URLs, internal linking and schema markup.

0 days

SALES DOWNTIME

100%

URLS PRESERVED

−2%

ORGANIC TRAFFIC M+1

→

Topeshop

PRESTASHOP → SHOPIFY PLUS FASHION D2C GLOBAL EU

PrestaShop → Shopify Plus migration with 58% conversion uplift.

Fashion retailer with a 12k SKU catalog. Full migration to Shopify Plus for global European expansion. Stability, speed and trust in the Shopify brand in the EU as the basis for the platform decision.

+58%

CONVERSION

−71%

PDP PAGE TTFB

+22%

ORGANIC TRAFFIC YOY

→

03 Migration FAQ

Migration questions we hear most often.

How much do we really lose in search rankings after a migration?

It depends on the quality of the migration process. The industry benchmark for migrations without an SEO-first approach is a 15-30% drop in organic traffic in the first three months, recovering over 6-12 months. In our migrations, the average drop is under 3%, thanks to full one-to-one URL mapping, SEO validation before launch, and 90 days of post-launch monitoring included in the price. If we see a drop above 5% in the first month, we fix it at no extra cost.

Does the store have to go offline during the migration?

No. We run the production cutover during a low-traffic window (typically Sunday night), with full monitoring for 72 hours. The store stays available to customers throughout the process. Every migration we've done in the last three years has had zero days of sales downtime — it's one of our contractual guarantees. In extreme cases (like the Bogart Meble migration from PHP 5.4), the cutover required three stages spread over time, but each one happened in a low-traffic window without taking the store offline.

What happens if we notice a traffic drop after the migration?

90 days of post-launch monitoring is included in the price of every migration. Weekly reports cover organic traffic monitoring (Google Search Console plus Ahrefs), 404 detection, indexation verification, and Core Web Vitals regression alerts. If we see a drop above 5%, we fix it at no extra cost. In practice, no post-launch fix was needed in 95% of our migrations — the SEO-first process protects this area already at the design stage.

How long does a mid-market store migration take?

It depends on the scenario and catalog scale. PrestaShop → Shopify Plus for a catalog of up to 10k SKUs typically takes 8-14 weeks. PrestaShop → Sylius headless for a 10-50k SKU catalog takes 14-22 weeks. Legacy PHP → Symfony for years-old custom code takes 22-40 weeks (the longest scenario, since it requires rebuilding the entire business logic). After a free initial audit, you get a concrete timeframe accurate to within two weeks.

Do we sign a contract with penalties for missed terms?

Yes. Every migration is signed as a fixed-price contract with concrete SLA milestones and contractual penalties for missed deadlines or SEO guarantees. Standard penalty for exceeding the launch deadline is 0.5% of the project value per week of delay that's our fault. The penalty for an organic traffic drop above 5% in the first 90 days is 10% of the project value plus a fix at no extra cost. These are real client-protection mechanisms, not marketing.

What happens to the store after the migration — are we left without support?

After 90 days of post-launch monitoring (included in the migration price), most clients move to ongoing care under one of two models — an SLA and Help Desk package (from PLN 950/month for Basic, up to PLN 3,800 for Premium) or a Growth Retainer (from PLN 12k/month for Maintenance, up to PLN 45k for Enterprise). The average relationship length with SLA and Growth Retainer clients is 3.4 years. Nobody is forced into long-term commitments — you can also end the engagement after the migration and move to external support.

FIRST STEP

Your migration starts with a free audit.

The free initial audit is two hours of analysis of your current store — SEO baseline, URL structure, code quality, potential migration risks. After the audit, you get a preliminary estimate accurate to ±20% and a recommended migration scenario. If it turns out we're not the right fit, we'll recommend another provider.

Book a free audit → Fill in the project brief →