Why we do not rewrite the backend in headless migration from 1C-Bitrix
By: WebGoodPeople, Founder, WebGoodPeople
The main client fear
When we say "headless," clients usually hear "we need to rewrite the entire backend." That is a misunderstanding worth clearing up from the start.
Your 1C-Bitrix with its catalog, pricing, orders, 1C integration and CRM — stays exactly as is. We change only what the buyer sees: the frontend.
What headless means in our context
Headless means the backend (CMS, catalog, business logic) is decoupled from the frontend. Classic Bitrix runs as a monolith: backend and frontend are one. In our setup: Bitrix stays as is, Elasticsearch handles search and filtering, Next.js is the frontend.
Why rewriting the backend is a bad idea
We have seen projects where an agency persuaded clients to switch stacks at the same time. Result: 12–18 months of development, lost business logic, broken integrations. Your Bitrix contains years of work — B2B pricing rules, 1C warehouse integrations, role-based visibility, marketplace connections. Why touch what works?
How it works in practice
Our process starts with Catalog Probe — in 3 days we take your catalog (CSV or XML from Bitrix), index it in Elasticsearch, and show a live frontend prototype with your actual products. Not a single backend line touched. This eliminates the main risk: you see the real result before committing to a full project. After that — iterative development, old site running in parallel until cutover.
Real results
UralMetall — metal products, 20,000+ SKUs. Headless frontend on existing Bitrix, no backend changes. Result: SEO traffic ×3.5, Core Web Vitals green across all metrics.
Vostok-Watches24 — international watch store. One Bitrix backend serving 3 markets with different prices and localization. No backend rework — we added Elasticsearch and a Next.js layer.
What this means for you
If you have a working Bitrix store and want a better frontend — you do not need to rebuild everything. You need to add a layer that handles what the buyer sees. Catalog Probe — live prototype in 3 days.