Updating the Bitrix core breaks sites more often than admitted. Not because the core is bad, but because most custom code violates the principle "don't touch the core": edits in bitrix/modules/, direct calls to deprecated functions, reliance on internal component structure. The update reveals this debt.
We have 10+ years of experience updating sites on 1C-Bitrix — from simple online stores to portals with custom modules and 1C integrations. We know which errors are typical and how to prevent them. If an update is done without preparation, the site can be down for hours or days — loss of orders and reputation. The right approach is audit, staging, phased testing. We guarantee operability after the update: each stage is documented, custom code is adapted, you receive a checklist and a plan for future updates. The probability of failure is reduced by 90% compared to a self-performed update.
Why does the update break the site?
Direct edits to core files. bitrix/modules/catalog/install/components/bitrix/catalog.element/templates/.default/template.php — manually edited. After the update — overwritten with the original. Anything inside /bitrix/ that was modified is lost.
Deprecated functions. Every few versions, Bitrix declares functions deprecated and eventually removes them. Calling CIBlockElement::GetList() with incorrect parameters may behave differently than before. Calling a removed method — Fatal Error.
Changes in module APIs. The sale module was seriously reworked: the old API (CSaleOrder::Add) coexists with the new one (Bitrix\Sale\Order), but behavior in edge cases may differ.
Custom modules from Marketplace. If the module developer hasn't updated it for the new core version — after the update the module may not work.
How do we conduct the update?
We use a refined process that minimizes risks.
- Code audit. Check for edits inside
/bitrix/(viagit difforfind /bitrix -newer /bitrix/bitrix_version.php -type f), calls to deprecated functions (grep onlocal/), and Marketplace module compatibility. - Deploy staging. Full copy of production with the same PHP version, external integrations disabled.
- Update on staging. Use the console tool
/bitrix/bin/console update— this removes time execution limits. - Testing. Go through critical scenarios: homepage, catalog, product card, cart, checkout, personal account, admin panel. Check error log.
- Deploy to production. In maintenance mode, after full testing. Check logs again.
| Stage | Duration |
|---|---|
| Audit and preparation | 0.5–1 day |
| Update on staging | 0.5–2 days |
| Testing | 0.5–2 days |
| Deploy to production | 1–2 hours |
What is included in the work?
After the update, you receive:
- Full report on changed files and code adaptation.
- Checklist for site functionality verification.
- Plan for subsequent updates with recommended frequency.
- Guarantee on the operability of critical functions for 30 days.
- Consultation on further version support.
Why trust us with the update?
We are certified 1C-Bitrix specialists with 10+ years of experience and 500+ successful updates. Compared to self-updating, our approach reduces downtime by 2–3 times and eliminates typical errors.
| Criterion | Self-update | Our service |
|---|---|---|
| Code audit | Often skipped | Mandatory step |
| Staging | Rare | Always |
| Testing | Surface-level | Full scenario coverage |
| Guarantee | None | 30 days |
| Failure risk | High | Minimal |
Preventing a single crash after an update can save you hundreds of thousands of rubles in emergency recovery. Contact us — we will assess your project and offer a timeline and cost individually.
Typical errors during update
- Direct edits in
/bitrix/— overwritten during update. - Using deprecated functions —
CIBlockElement::GetList()with incorrect parameters. - Marketplace module incompatibility — developer hasn't released an update.
Timelines
| Situation | Timeline |
|---|---|
| Regular update (gap up to 3 months) | 1–2 days |
| Update after 6–12 months of inactivity | 3–5 days |
| Update with 1.5–2 year gap | 1–2 weeks |
| Update with 3+ year gap + custom code | 2–4 weeks |
The main variable is the amount of custom code that needs adaptation. A site on standard components with code in local/ is easier to update than a site with core edits and five-year-old custom modules.
Official 1C-Bitrix update guide confirms the need for custom code audit and staging testing. We strictly follow these recommendations.
Get a consultation — contact us, we will assess your project and offer a timeline and cost individually. Order an update with a 30-day guarantee.