webgoodpeople Logo
Contact

Service · Headless e-commerce

5× faster store — backend untouched

A slow store loses conversion and search rankings. 1C, Bitrix, CRM, ERP and marketplace integrations stay exactly as they are. We move only the storefront to Next.js + Elasticsearch. The store keeps running. First numbers in 3–5 weeks: ur-met.ru grew organic traffic 3.5×, vostok-watches24 returns search queries in 88ms.

Message us on TelegramGet a migration plan
  • Pilot in 3–5 weeks
  • Full replatform in 2–4 months
  • Zero-downtime
  • Fixed price
Web storefront
iOS + Android
PWA

Frontbox · core

Next.js + Elasticsearch

SSR · ISR · edge cache · facets · synonyms · auth

~120msTTFB
1.9sLCP
88mssearch
1C‑Bitrix
1C
CRM / ERP

What changes

Four results your customers and marketers will notice

  • LCP 1.5–2s on mobile

    A Bitrix monolith hits PHP/MySQL limits — you feel it when the catalog grows. Next.js + edge caching brings LCP to 1.5–2s on 4G. Mobile checkout conversion grows 15–30%.

    was 3.5–4s → now 1.5–2s

  • 88ms search

    Elasticsearch with morphology, synonyms, facets and autocomplete. Zero-result share converges to zero.

    < 100ms at 100k+ products

  • Your Bitrix team keeps working

    Developers keep owning the business logic in Bitrix. We don't need access to 1C and don't touch business processes.

    zero backend changes

  • ×3.5 organic traffic without losses

    1:1 URL structure, 301 redirects, full meta / JSON-LD / sitemap carry-over. Core Web Vitals go green — Google and Yandex notice.

    ur-met.ru: ×3.5 in 3 months

Live projects

Already running on Frontbox

Real stores that moved to Frontbox without replacing the backend.

Benchmarks

Numbers Google and Yandex reward

  • LCP
    1.5–2s
    Largest Contentful Paint on 4G. Was 3.5–4s.
  • TTFB
    ~90–150ms
    Time to first byte on edge cache.
  • Search
    < 100ms
    Elasticsearch query with facets at 100k+ products.
  • INP
    < 200ms
    Interface responsiveness per Core Web Vitals.

How the migration runs

Four phases — store stays live throughout

We don't touch your backend. We connect via API and webhooks, then gradually shift traffic — the old site runs in parallel the whole time.

  1. 013–5 days

    Catalog Probe

    We load your catalog (CSV/XML) into Frontbox and deploy a preview. Integration audit: 1C, Bitrix, payments, delivery, marketplaces, analytics.

  2. 022–4 weeks

    One-category pilot

    Full scope — PDP, listing, cart, checkout, payment — runs live on a separate subdomain. We share metrics: LCP, conversion, SEO positions.

  3. 034–8 weeks

    Gradual traffic cutover

    A/B test: Frontbox share scales from 5% to 100%. Old site runs in parallel. Instant rollback — one command.

  4. 042–4 months from start

    Full replatform and handoff

    Full cutover. Docs, runbooks, CI/CD handed over to you. Optional retainer with 99.9% SLA.

Data flow

Your backend stays. Frontbox is a separate layer.

source

1C-Bitrix + 1C

sync

Webhook · queue

frontbox

Next.js + ES

Why this is safe

Migration without business risk

You know what downtime costs. Every phase is designed so rollback takes seconds, not hours.

  • Bitrix backend and 1C untouched

    Your developers and business processes keep running as usual. No data migration, no changes to 1C exchange.

  • Store runs without downtime

    Frontbox launches on a subdomain, traffic shifts gradually via A/B. Instant rollback — one command — at any point.

  • SEO preserved

    URL structure stays 1:1. Where URLs change — full 301 map. Meta, JSON-LD, sitemap carried over automatically.

  • You see metrics before committing

    A pilot on one category runs live — with LCP, conversion and SEO positions — before you commit to Full Replatform.

Comparison

Headless migration vs classic redesign

Two paths to a fast store. A classic redesign is a big project with platform replacement. Our migration changes only the storefront — backend and team stay put.

What matters
Headless migration WGP
Classic redesign
  • Backend
    Untouched — 1C, Bitrix, ERP stay as is
    Often requires replacement or deep rework
  • Launch timeline
    Pilot — 3–5 weeks, full store — 2–4 months
    4–12 months, no guarantees
  • Store downtime
    Zero — A/B test, rollback in one command
    Hours or days at cutover
  • Cost
    fixed price · quote in 48h
    3–10M RUB upfront
  • SEO on cutover
    1:1 URLs, 301, meta, JSON-LD, sitemap — all carried over
    Risk of ranking drops if URL structure changes
  • Rollback
    Instant — one deploy
    Complex and costly

Two engagement formats

Pilot or Full Replatform — your choice

Not sure about the outcome? Start with a pilot in 3–5 weeks and see real numbers before committing. Goal already clear — go straight to a full replatform. Fixed price for both.

Entry · Catalog Probe + Pilot

Validate in 3–5 weeks

We load your catalog into Frontbox, deploy a preview, and run one category live on a subdomain. Metrics go to you and your board.

on requestfixed price

Fee credited toward Full Replatform

Timeline
3–5 weeks
Where it runs
your subdomain
What you get
metrics before the final decision
  • Catalog Probe: CSV/XML load, preview deployment on subdomain
  • Integration audit: 1C, payments, delivery, marketplaces
  • One full scope live: PDP, listing, cart, checkout, payment
  • Report: LCP before/after, conversion, SEO positions on key queries
  • Fixed price — no hourly overages
Start the pilot
Full Replatform

Full Replatform · entire store

Zero-downtime in 2–4 months

A/B traffic cutover from 5% to 100%. Old site runs in parallel. Docs, CI/CD, runbook handed over to you. Optional retainer with 99.9% SLA.

on requestfixed price

Pilot fee credited if already completed

Timeline
2–4 months
Where it runs
your domain
What you get
code + CI/CD + docs
  • All 4 phases: Catalog Probe → Pilot → Gradual cutover → Handoff
  • A/B test with Frontbox share scaling from 5% to 100%
  • Instant rollback at any point — one command
  • SEO carry-over: 1:1 URLs, 301 redirects, meta, JSON-LD, sitemap
  • Docs, runbook, CI/CD — handed to your team
  • Option: retainer with 99.9% SLA and KPI bonus after handoff
Get a migration plan

Format comparison

ParameterPilotFull Replatform
Timeline3–5 weeks2–4 months
ScopeOne category on subdomainEntire store on main domain
What you getMetrics before the decisionCode + CI/CD + docs
RiskMinimal — testing the hypothesisZero — A/B, rollback anytime
Next stepCredited toward Full ReplatformOptional retainer with 99.9% SLA

Formats can be combined: the pilot fee is credited toward Full Replatform if you continue.

FAQ

Common migration questions

  • Do we have to move off 1C-Bitrix?

    No. Frontbox is a frontend on top of Bitrix via API. Backend, license, 1C exchange, all integrations stay as they are. Your Bitrix team keeps working as usual.

  • Our developers work on Bitrix — what happens to them after migration?

    Nothing changes. All business logic stays in Bitrix: catalog, orders, users, 1C integrations. Developers keep owning the backend. The frontend team is ours or yours by arrangement.

  • Can we migrate without taking the store down?

    Yes. Frontbox launches in parallel on a subdomain. Traffic shifts via A/B: first 5%, then 20%, 50%, 100%. The old site runs the whole time. Rollback — one deploy command.

  • We're on a custom Bitrix Enterprise build — does it fit?

    Yes. We integrate via REST/SOAP/webhooks available in all Bitrix builds from version 20.x. Custom logic stays on the backend; the frontend only consumes the API.

  • What happens to SEO during traffic cutover?

    URL structure stays 1:1 — every URL in Bitrix maps to the same URL in Frontbox. Where URLs change — full 301 map. Meta, og:, Product JSON-LD, BreadcrumbList and sitemap are carried over automatically. Core Web Vitals improve right away — a positive ranking signal.

  • How much does a 10,000-SKU migration cost?

    We send a written fixed-price quote with options within 48 hours of a short brief. Final number depends on integrations, unique business processes, and whether an AI layer is in scope. A Headless Pilot for one category starts from $5,500.

  • What about marketplace integrations — WB, Ozon, Kaspi?

    Nothing to do. Marketplace integrations run on the Bitrix/1C side — Frontbox doesn't touch them. WB, Ozon, Kaspi, CDEK, DataLens keep working without edits.

  • What is Catalog Probe and why do we need it?

    It's the first phase: we load your catalog (CSV/XML) into Frontbox and deploy a preview. You see how the new storefront looks and works before we touch anything in your production environment. Zero risk at entry.

  • What's included in the handoff after Full Replatform?

    Architecture docs, runbook (incident and update procedures), configured CI/CD in your repository, team onboarding. After handoff you run the project independently or take a retainer with 99.9% SLA.

Pilot live in 3–5 weeks

See metrics before the final commitment. Backend untouched.

Message us on TelegramGet a migration plan via the form →

What to read next - Related content and services

Message on Telegram