Astros Logistics: CMS → clean markup

About the client

Astros Logistics (astroslogistics.ru) is a large logistics operator: warehouses, freight, foreign trade, helping foreign brands enter the Russian market.

They came to us not to “redraw the brand”, but to remove CMS dependence: a heavy platform was blocking normal site life and iterations. The job - rewrite to clean markup while keeping the familiar storefront.

The challenge we started with

Move off the CMS without "breaking everything and starting from scratch"
Transfer the storefront 1:1: header, service menu, hero, figures, cards
Restore the logic: mega menu, slider, anchors/forms, RU/EN
Hand over clean code so the client's in-house developers can continue the design

Client request

The company came with a specific brief: rewrite the CMS site as clean markup. Not a new marketing concept from scratch, but a technical way out of the platform's limitations - so the site could be properly developed by their own staff.

1:1 migration

We carried over the structure and meaning of the pages one to one: header and languages, yellow service navigation, hero with slider, the "Astros in numbers" block, service cards (import, entering the Russian market, warehouse, high-value cargo, etc.). The screenshots show the result of this migration.

Full logic restoration

Not just "a picture in HTML". We restored the behavior: service mega menu with nested items, hero slider, CTA to the form, RU/EN switching, the links between service blocks. So that after leaving the CMS the site behaves like the familiar storefront, not a static mockup.

Handover to the internal team

After the migration and logic restoration, we handed the project over to the company. Design and iterations were then led by their own developers - our responsibility was a clean base: markup plus logic with no CMS lock-in.

Gallery

ASTRO LOGISTICS: CMS to clean markup migration - screenshot 1

ASTRO LOGISTICS: CMS to clean markup migration - screenshot 2

ASTRO LOGISTICS: CMS to clean markup migration - screenshot 3

How it works

User scenario

Visits astroslogistics.ru like the familiar storefront
Browses services via the menu / cards
Submits a request / contacts the company

Team / admin scenario

The client's internal team develops the design on a clean base
No vendor lock-in to a heavy CMS at every step
Menu, slider and form logic is already restored

Technology

Before: CMS-based site
After: Clean markup + logic
Type of work: 1:1 migration
After handover: Client's internal team

Timeline: CMS → code migration

Result and business effect

Astros Logistics site rewritten from CMS to clean markup: 1:1 migration and full logic restoration. Project handed to the company - further design and development by their internal engineers. Public storefront: https://astroslogistics.ru/. Screenshots of home, services menu, and stats block in the gallery.

A fit if you need

You need to move from a CMS to clean markup without breaking the concept - Websites
You need a 1:1 migration and restoration of complex menu/form logic - Web applications
An internal team will continue the project after handover - SLA support

Frequently asked questions

Questions about this type of project, the same ones clients ask before a similar build.

Why not use amoCRM or Bitrix24 off the shelf?

If the boxed product covers your process, we keep it and extend it. Custom CRM development makes sense when the template breaks your sales: your own stages, a complex client cabinet, reports, a tight link with 1C. A common setup is a boxed CRM for sales plus a custom module next to it.

How do we move off Excel without stopping work?

In stages. First a new setup for one or two roles while Excel keeps running. We migrate statuses and reference data, reconcile, train people — and only then switch the spreadsheets off.

Will you rework our 1C configuration?

No. By default we build an external API exchange with an error log and mismatch checks — not “manual exports once a week”. Changes inside a standard 1C configuration happen only under a separate spec, together with your 1C partner if needed.

Who owns the code, and what if our processes change?

The code and infrastructure stay with you. New processes come in as modules: each is estimated separately, with acceptance criteria agreed before coding.