+7 (700) 700 71 77 info@oneit.kz
Astro + 1C-Bitrix

Your Astro site loads instantly, and you manage it in 1C-Bitrix

We move your site's front end to Astro: pages reach visitors fully rendered and don't slow down under bot traffic. The catalog, prices, stock, orders, 1C sync and Bitrix24 leads stay in Bitrix — content managers keep working in the same admin panel as before.

The browser gets a ready page from the Astro cache; Astro takes data from 1C-Bitrix: products, prices, orders, 1C, Bitrix24, SEO
3Astro sitesin production: onelab.kz, onehost.kz, oneit.kz
100Speed scoreLighthouse mobile: oneit.kz and onelab.kz
98%Less work for Bitrixof pages on oneit.kz it no longer renders
1 minTo roll back any sectionwe migrate section by section, with no sales downtime

Why

Why a Bitrix site is slow even on a good server

Bitrix is a strong admin panel and back end: catalog, orders, 1C, permissions, CRM. But rendering every page for every visitor is not its strong suit. That is exactly the job Astro takes over.

1CBitrix front end

  • On every visit, PHP rebuilds the page from scratch: template, components, dozens of database queries. Composite mode and caching help, but they are reset by the 1C sync and don't work for logged-in users.
  • Off-the-shelf store templates pull in jQuery and dozens of CSS and JS files — on a phone, the page “thinks” for seconds.
  • Search engine crawlers, AI bots and price scrapers open thousands of pages — each one ties up the CPU and the PHP queue while the customer waits.
  • Updates to the core and the ready-made solution affect the template: the layout has to be rechecked after every update.

AAstro front end

  • A page is built in advance or once on the first request — after that, visitors get ready HTML from the cache.
  • Only the scripts that are needed reach the browser: menu, cart, filter. The rest is plain HTML and CSS, so the site is fast even on a low-end phone.
  • Bitrix only handles the data: a lightweight “give me this section or product” request instead of building the whole page.
  • The layout lives in Git, separate from Bitrix: core updates don't touch it, and every change is verified by a build before it goes live.

Options

Three ways to move to Astro

We choose based on what the site needs: a cart, a customer account, 1C sync — and how big the catalog is.

Fully on Astro

Corporate sites, landing pages, blogs and help sections. No PHP and no database on the server — nothing to hack and nothing to update. Texts are edited in a simple panel, and publishing takes a couple of minutes.

In action: onelab.kz and onehost.kz — both used to run on Bitrix.

Astro front end + Bitrix admin

Online stores, catalogs, sites with a customer account. Visitors see Astro, while products, prices, stock, SEO fields, orders, 1C sync and Bitrix24 stay in Bitrix. A catalog of any size is rendered on request and kept in the cache.

In action: oneit.kz — a catalog of tens of thousands of products.

Step-by-step migration

For a live Bitrix site: we move it section by section, on the same domain and the same URLs. Each section is switched on separately and can be switched back just as quickly — the Bitrix template is not deleted.

Sales and SEO don't stop for a single day.

Architecture

Bitrix stays the brain of the site, Astro becomes its face

The content manager works in the Bitrix admin panel as before. Our module serves page data, Astro turns it into ready pages, and nginx keeps them in the cache.

1Content managerChanges a product, price, banner or article — in the familiar admin panel.
21C-Bitrix admin panelInfoblocks, prices and stock, supplier imports, 1C sync, SEO fields.
3Data export moduleServes each page as data: section, product, filter, search, menu, banners. Access by key only.
4AstroStatic pages — at build time, hourly and at the push of a button. Catalog, search and filter — rendered on request by a Node.js page server.
5VisitorGets a ready page from the nginx cache. Cart, checkout and account still run on Bitrix.

Stays in Bitrix

  • Admin panel, staff and access permissions.
  • Catalog, prices, stock, supplier imports and 1C sync.
  • Cart, checkout, payment, customer account.
  • SEO fields, page URLs, sitemap.
  • Form submissions — to web forms, Bitrix24 tasks and managers' email.
  • License, core and module updates.

Handled by Astro

  • All public pages: home, catalog, product pages, search, smart filter, brands, blog, help.
  • Header with cart, favorites and customer name — loaded by a separate lightweight request, while the page itself stays cached.
  • Lead forms with spam protection.
  • Redirects from old URLs and parameters.
  • The “page not found” page and redirects from out-of-stock product pages to their section.
  • If Bitrix is down, catalog pages are served from the cache.

Case study

oneit.kz: a Bitrix store that moved to Astro

An online computer hardware store: 1C-Bitrix with the Aspro ready-made solution, a catalog of tens of thousands of products, daily supplier imports, 1C sync, Bitrix24 leads. We moved the front end to Astro section by section without halting sales for a single day.

InventoryAll pages and templates, forms, orders, integrations, indexed URLs, bots and load.
Static pagesHome, help, company, contacts, blog, services, brands — over 200 pages from the build.
FormsSubmissions go to Bitrix web forms, to Bitrix24 as a task and by email to the responsible manager.
ConfiguratorRefurbished servers section: 75 models with configuration price calculation.
CatalogSections, product pages, smart filter, search and brands — rendered on request by the page server, with caching.
−98%pages rendered by Bitrix: 22 per hour instead of 1,317 — Astro serves the rest
100Lighthouse mobile speed score for the home page, a catalog section and a product page; SEO is 100 too
~250404 responses a day instead of 7–10 thousand: out-of-stock product pages lead to their section
0days of sales downtime: each section was switched over separately and could be rolled back in a minute
Admin panel unchangedManagers edit products, banners and articles in Bitrix as before. The front end and Astro can be updated with a button in the admin panel.
Bots no longer get in the waySearch engines and price scrapers crawl the catalog through the cache, and frequent requests from a single address are rate-limited.
Up to 100 on our own site, tooOur “Bitrix24 Implementation” page on onelab.kz scored 75 on mobile; after our fixes it hit 100 the same day. We take the same approach in every project.

What we've covered

Pitfalls we've already hit, so you don't have to

Moving the front end is more than markup. Here is what we check on every project — because each of these has tripped us up before.

01No SEO losses

The same URLs, titles and descriptions from Bitrix SEO settings, sitemap and structured data. Old URLs with parameters get permanent redirects.

02Page-by-page check

We compare every migrated page with the original: texts, prices, specs, links, headings. Discrepancies are fixed before the switchover, not after complaints.

03Cart and customer

The page is the same for everyone and sits in the cache, while the header loads the cart, favorites and customer name with a separate request.

04Out-of-stock products

The product page temporarily redirects to its section; a disabled product redirects permanently. Once it's back in stock, the page opens at its old URL again.

05Bots and price scrapers

Search engines crawl without limits, while excessively frequent requests from a single address are refused. The cache can handle a full catalog crawl.

06Monitoring

Availability checks for key pages, a separate check of the module's handlers, and a front-end status report right in the Bitrix admin panel.

07Updates

Astro and Node.js versions are pinned, and updating takes one button: build, check, deploy — and if anything fails, a rollback to the previous version.

08Security

The page server runs in isolation and can't see Bitrix files, deployment uses a separate key limited to the front end, and the module serves data only with a key.

Comparison

What changes for the site and the team

A hybrid doesn't replace Bitrix — it takes over the work Bitrix does worst.

Bitrix as isAstro + BitrixAstro only
Mobile speedDepends on the template and composite mode; often secondsReady page from cacheReady page from disk
Server loadPHP and the database for every pagePHP only serves dataNo PHP or database
Where content is editedBitrix admin panelBitrix admin panelSimple panel or Git
Catalog, 1C, orders, CRMYesYes, in BitrixVia separate services
Cart and customer accountYesYes, in BitrixNo
UpdatesCore and solution updates affect the templateFront end separate from the coreAstro only
Best forSites that are already fast, with nothing to changeStores, catalogs, portalsCorporate sites, landing pages, blogs

Scroll the table sideways →

How we work

How the migration goes

Timelines are guidelines for a mid-sized store. A corporate site moves faster; we give an exact estimate after the audit.

01

Site audit 3–5 days

Pages and templates, forms, 1C and Bitrix24 integrations, indexed URLs, load and bots. The result: a section-by-section migration plan and a cost estimate for each stage.

02

Front end on a private URL 1–3 weeks

Astro layout with real data from your Bitrix. We show it, refine it and compare it with your current site page by page.

03

Data export module in parallel

We install a module on your Bitrix that serves page data. The admin panel and staff permissions stay the same.

04

Section-by-section switchover from a day per section

Static pages, forms, catalog, home page — each section is switched on separately, checked and, if needed, rolled back in a minute.

05

Post-launch monitoring 1–2 weeks

Server responses, redirects, sitemap, Search Console and Yandex Webmaster, load and bots. Minor issues are fixed right away.

06

Ongoing support

Astro, Node.js and Bitrix updates, new sections and blocks, technical support and hosting on our ONEHOST platform in Kazakhstan.

FAQ

FAQ

Will we lose search rankings?

Page URLs stay the same, titles and descriptions come from Bitrix SEO settings, the sitemap and structured data are preserved, and old URLs with parameters get permanent redirects. Fast pages only help with search engines. After the switchover, we monitor Search Console and Yandex Webmaster.

Will content managers have to retrain?

No. Products, sections, banners, articles and SEO fields are edited in the same Bitrix admin panel. The catalog on the site updates within five minutes; other pages update with the hourly build or instantly with a button in the admin panel.

Do we need a 1C-Bitrix license?

For the hybrid, yes: Bitrix runs as before, with its license, updates and modules. A fully static site doesn't need Bitrix.

What happens to 1C, orders and Bitrix24?

Everything stays in Bitrix and works as before: 1C sync, cart, checkout and payment, CRM leads. The front end only displays the data.

What if Bitrix goes down?

Static pages work without it, and catalog pages are served from the cache. Orders can't be placed during that time — just as today when Bitrix is down.

Can we go back to how it was?

Yes. Each section is switched separately and can be reverted in a minute, while the Bitrix template stays in place.

Is this right for our site?

Yes, if your Bitrix site is slow, suffers from bots, or its template is hard to develop further. You don't need it if the site is already fast and no changes are planned. For a portal with a large customer account area, we move only the public part.

Where is the front end hosted, and how much does the migration cost?

On your server next to Bitrix, or with us at ONEHOST in Kazakhstan: static pages need only nginx, while an on-request catalog needs Node.js. The cost depends on the number of page templates, integrations and the catalog size — after the audit we provide a stage-by-stage estimate, and each stage can be accepted separately.

Discuss the move

Send us your website address — we will estimate what Astro will give you

We will look at speed, the template, server load and bots, and tell you which option suits your website and which section to move first.

  • We reply within a business day and meet online or at our office in Almaty or Astana.
  • We will show live how oneit.kz, onelab.kz and onehost.kz are built.
  • A corporate website we estimate right away, an online store after a short audit.

Have a specification or a list of improvements? Send it to info@oneit.kz (PDF, DOCX, XLSX up to 20 MB) — and mention it in your message.

0/500