Service · Headless e‑commerce - Your Bitrix stays. We only change what your customers see.
1C, Bitrix, CRM, ERP, marketplace integrations — all stay exactly as they are. We move only the storefront to a fast Next.js front‑end. Your store keeps running without downtime, business processes stay intact, and your Bitrix team keeps working in their usual environment. Pilot in 2–4 weeks, full replatform in 2–4 months.
Case · UralMetall · ur‑met.ru
×3.5organic traffic growth
×8faster to ship changes
All greenCore Web Vitals
Case · Vostok‑Watches24
3 marketson one backend
88 mssearch response
TTFB 120 mstime to first byte
Pains we solve - What usually hurts on 1C‑Bitrix e‑commerce
- LCP 3.5–4s and mobile SEO decline. A Bitrix monolith is capped by PHP and MySQL. We push LCP to 1.5–2s on 4G via SSR/ISR and edge caching. Mobile checkout conversion grows 15–30% (Dallas luxury retailer, Meerako case, 2025).
- Slow filters and empty search results. Elasticsearch with morphology, synonyms, facets and suggestions. Query latency under 100ms. Zero‑result share converges to zero.
- 1C / CRM / site data drift. We build a data contour with a single source of truth. Sync jobs are monitored, with proactive alerts to Telegram/Slack on stock or price mismatches.
- Enterprise license cost. Bitrix Enterprise renewal is 487,500 RUB/year. With Frontbox you can stay on a basic Bitrix tier or migrate to an open‑source backend long‑term — your choice.
How the migration runs - Four phases — downtime stays on us, not on you
- Phase 1 · Catalog Probe & discovery · 3–5 days. We load your CSV/XML catalog into Frontbox and deploy a preview. Integration audit: 1C, Bitrix, payments, delivery, marketplaces, analytics.
- Phase 2 · One‑category pilot · 2–4 weeks. One full scope (PDP, listing, cart, checkout, payment) runs in production on a separate subdomain. We share before/after metrics with your CFO and board.
- Phase 3 · Gradual traffic cutover · 4–8 weeks. A/B test, scaling Frontbox share from 5% to 100%. Old site runs in parallel, instant rollback is one command away.
- Phase 4 · Full replatform and handoff · 2–4 months from start. Full cutover. Docs, runbooks, CI/CD — handed over to you. Optional retainer with 99.9% SLA and KPI bonus.
What stays on Bitrix - We don't touch the backend — only what the customer sees
- 1C exchange, products, stock, prices. All regular 1C exports keep flowing into Bitrix. Frontbox subscribes to webhooks/REST and indexes to Elasticsearch.
- Orders, statuses, payments. Checkout creates orders via Bitrix API. Statuses, numbers, EDI — unchanged. No migration in the sales team.
- Infoblocks, users, groups. All Bitrix structures are preserved. Your editors keep working in the familiar admin.
- Marketplaces, delivery, BI. WB, Ozon, Kaspi, CDEK, DataLens — all integrations keep working without edits.
SEO migration - How we preserve organic traffic during cutover
- 1:1 URL structure. Each /catalog/section/product on Bitrix maps to the exact same URL on Frontbox. No /products/123-slug where /catalog/category/product used to be.
- 301 redirects and canonical. Where URLs do change — a full 301 map. Canonical set automatically.
- Meta, schema and sitemap carry‑over. All meta, og:, Product JSON‑LD, BreadcrumbList — transferred. Sitemap is regenerated and pinged to search engines automatically.
- Top‑quartile Core Web Vitals. LCP < 2s, INP < 200ms, CLS < 0.1 — the threshold for top mobile rankings on Google.
FAQ - Common migration questions
- Do we have to move off 1C‑Bitrix?. No. Frontbox is a frontend on top of Bitrix via API. The backend stays, and so does your Bitrix Enterprise license cost.
- What about our Bitrix developers?. They keep owning the business logic in Bitrix. The frontend team can be yours or ours — your call.
- We're on a custom Enterprise build — does it fit?. Yes. We integrate via REST/SOAP/webhooks available in all Bitrix builds from 20.x up.
- How much does a 10,000‑SKU replatform cost?. Fixed‑price scoped to your project — we send a written 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.
What to read next - Related materials and services
Playbook
Bitrix → Next.js migration: 8 phases
Step‑by‑step plan with checklists, SEO map, and rollback.
CompareHeadless vs Bitrix optimization
10 selection criteria: LCP, TCO, vendor lock‑in, AI readiness.
GuideHow to pick a headless platform
Shopify vs commercetools vs Medusa vs Frontbox matrix.
ProductFrontbox — Next.js + Elasticsearch
$400/mo subscription, no capex project required.
ServiceAI Pilot with KPI
PDP personalization and semantic search on top of Frontbox.
ServiceRetainer + 99.9% SLA
Support with financial penalty on downtime.
Tell us about your project
Our offices
- Russia
Saint Petersburg, Rizhskaya st. 5, bldg. 1, office 402
+7 (967) 555-90-32 - Kazakhstan
Almaty
+7 (707) 340-29-12