Services

1C-Bitrix website support

Updates that keep your customisations, composite cache, ERP exchange, licensing and performance. Legacy Bitrix projects kept steady.

Timelinemonthly

What's included

Core and module updates
Moving edits out of /bitrix/
Composite cache configuration
ERP exchange diagnostics
Licence tracking and renewal
Performance tuning
Backups and monitoring

1C-Bitrix is a Russian enterprise CMS with a large installed base across Eastern Europe and Central Asia. If you are reading this in English, you most likely inherited a Bitrix project rather than chose one: an acquired subsidiary, a regional division, or a partner site that has to keep running. That is exactly the situation this service is built for.

Bitrix does a great deal out of the box, and you pay for that in hosting requirements, a paid licence, and updates that argue with customisations. A typical project accumulates layers of modifications nobody documented, so every update becomes a stress test. The classic mistake is editing components directly inside the /bitrix/ directory because it is quicker — which works right up until the first update overwrites everything with stock files. The correct home is /local/, and the first job on an inherited project is often migrating someone else's legacy there.

How we work

Project inventory. We check the edition and core version, licence status, installed modules, where custom components and templates live, and whether ERP exchange is configured. We write down what will break on update.
Move customisations to /local/. If edits live in the core, we relocate them somewhere updates won't touch. One-off work that saves months afterwards.
Updates on a copy. Bitrix only gets updated after a rehearsal on staging: we verify custom components survived, and that cart and customer account still work.
Composite cache. We configure composite caching and diagnose why it serves stale prices or another visitor's cart — a common and genuinely damaging failure.
ERP exchange. We watch the data flows: stock levels, prices, orders. When exchange stops silently and the catalogue drifts a week into the past, we catch it early.
Performance. Bitrix is resource-hungry. We profile slow queries, review cache settings and the built-in performance panel, and size hosting realistically.

What you get

Updates stop being an event people dread. Customisations survive upgrades because they finally live in the right place. The licence gets renewed on time rather than after vendor support lapses and security updates quietly stop arriving. Data exchange is monitored, so stock mismatches surface before a customer orders something that isn't in the warehouse.

For online stores the technical work usually pairs with catalogue and content upkeep — that's e-commerce support. General terms, response times and plans are on the technical support page.

Timeline

Onboarding runs from three days to a week. Bitrix takes longer to map than a mainstream CMS, especially when several contractors have passed through the project. After that we work month to month: scheduled updates on a calendar, critical security patches immediately. Migrating edits out of the core is quoted separately as one-off work, since the volume depends entirely on what previous developers left behind.

A typical scenario

Picture a corporate portal that hasn't been updated in two years because nobody wants to be the one who breaks it. The licence has expired, which means no security updates are arriving at all. The sensible sequence is licence renewal first, then a snapshot and an inventory of modifications — several of which turn out to sit in the core and need relocating to /local/. The update is rehearsed on staging, where two custom components surface as needing rework against the new API. Only then does the update reach the live portal, this time without surprises.

FAQ

Our Bitrix licence expired. What does that mean?

The site keeps running, but it stops receiving updates, security patches included. Over time that becomes real exposure: known vulnerabilities stay open on your installation. Renewal is the first step before any other work.

The previous developer edited files inside /bitrix/. Is that a problem?

It is, because updates overwrite those files with stock versions and functionality disappears without warning. The fix is migrating the edits to /local/ — one-off work whose size depends on how much was bolted on. After that, updating becomes safe.

What does Bitrix support cost?

It scales with the edition, the amount of custom code, and whether ERP exchange is in play. A store with integrations costs more than a brochure site on the same engine. We quote after the project inventory.

The composite cache shows customers outdated prices. Why?

Composite caching serves a whole cached page before dynamic areas render. If those areas are marked up incorrectly, visitors see data that isn't theirs — anything from a stale price to someone else's cart contents. The fix is correct markup and cache invalidation.

Our ERP exchange stopped and we noticed a week later. Is that normal?

It happens constantly, because exchange fails quietly: no errors on the site, data simply stops arriving. That's why monitoring the exchange with alerting is part of support — a failed sync tells us immediately rather than waiting for customer complaints.

Bitrix is slow. Can you help?

We start with the performance panel and slow queries, move to cache configuration, and only then discuss hosting. Often the bottleneck isn't hardware but inefficient queries inside custom components, and fixing those beats paying for a bigger server.

Will you take over a project you didn't build?

Yes, with a mandatory inventory first. Bitrix offers too many places to hide a modification, and accepting such a project blind would be unfair to the client. Once we've mapped it, we quote the scope honestly.

Message on Telegram → Message on MAX ← All services