Bitrix Refactoring to D7 ORM: Lower Support Costs

When we open a Bitrix project written several years ago, the first thing that catches the eye is global variables and concatenated SQL strings.

Clients complain about slow catalog performance, and every new feature request turns into rewriting half the code. One of our clients, an auto parts online store, was losing up to 15% of orders due to errors in delivery calculation caused by an outdated API. After refactoring to D7, we reduced the time to add new delivery methods from 3 days to 4 hours, and support costs dropped by 40%. In a project with 50,000 lines of code on the old API, every new feature cost three times more due to the need to work around global dependencies. Our refactoring is not "rewriting for the sake of rewriting" — it's about lowering support costs and eliminating the class of errors typical of procedural code. Support savings are substantial, with payback under 12 months. Contact us for a free assessment of your project.

What exactly changes when moving to D7

Global functions → DataManager methods:

// Before — old API
$res = CIBlockElement::GetList(
    ['SORT' => 'ASC'],
    ['IBLOCK_ID' => 5, 'ACTIVE' => 'Y'],
    false,
    ['nPageSize' => 20],
    ['ID', 'NAME', 'PROPERTY_PRICE']
);
while ($arItem = $res->GetNextElement()) {
    $arFields = $arItem->GetFields();
    $arProps  = $arItem->GetProperties();
}

// After — D7 ORM
$result = \Bitrix\Iblock\Elements\ElementProductsTable::getList([
    'select' => ['ID', 'NAME', 'PROPERTY_PRICE_VALUE'],
    'filter' => ['=IBLOCK_ID' => 5, '=ACTIVE' => 'Y'],
    'order'  => ['SORT' => 'ASC'],
    'limit'  => 20,
]);
foreach ($result->fetchCollection() as $element) {
    $name  = $element->getName();
    $price = $element->get('PROPERTY_PRICE_VALUE');
}

SQL strings → Connection API:

// Before — raw SQL with concatenation
global $DB;
$id = intval($id); // all the "protection"
$res = $DB->Query("SELECT * FROM b_custom_table WHERE ID = " . $id);

// After — parameterized queries
$connection = \Bitrix\Main\Application::getConnection();
$result = $connection->query(
    "SELECT * FROM my_custom_table WHERE ID = ?",
    [$id]
);
// or via SqlHelper for complex cases
$helper = $connection->getSqlHelper();
$safeId = $helper->forSql((string)$id);

Global $APPLICATION → Context and Application:

// Before
global $APPLICATION;
$APPLICATION->SetTitle('My page');
$APPLICATION->IncludeFile('/local/include/header.php');

// After — in component or controller context
$this->arResult['PAGE_TITLE'] = 'My page';
// Inclusion via D7 mechanisms or Inertia/React approach

Why the old API holds back development?

Security: concatenating SQL strings is a direct path to SQL injection. Performance: CIBlockElement::GetList() without limits dumps the entire table. Testability: global dependencies prevent isolating business logic. Read more about parameterized queries on Wikipedia.

How to carry out refactoring step by step?

Rewriting the entire project at once is a bad idea. Even a small online store contains 50,000+ lines of code. The right approach is layered refactoring with priority sorting.

What is included in D7 refactoring?

Full codebase audit identifying critical areas, creation of a service layer and migration to D7 ORM, replacement of SQL queries with parameterized ones via Connection::query, setup of tagged caching and agents, regression testing of each replacement, documentation of the new architecture, training your team on D7. Guarantee on work performed is fixed in the contract.

Infoblocks: migration to D7 classes

From the current Bitrix version, auto-generated classes for infoblocks are available via Bitrix\Iblock\Elements:

// Enable in infoblock settings — "API code" flag
// A class is generated with namespace Bitrix\Iblock\Elements

$result = \Bitrix\Iblock\Elements\ElementCatalogTable::getList([
    'select' => ['ID', 'NAME', 'IBLOCK_SECTION_ID'],
    'filter' => ['=ACTIVE' => 'Y'],
]);

This is not a complete replacement for CIBlockElement — for writing (add/update), the old API is often still used since D7 wrappers for infoblock writing do not cover all scenarios.

Typical pitfalls during refactoring

Loss of events. If old code called CIBlockElement::Update(), event handlers (OnAfterIBlockElementUpdate) were attached. When moving to D7 methods, ORM events are different. Requires checking which handlers are tied to old events.

Difference in GetList vs getList results. CIBlockElement::GetList returns infoblock properties in a specific format with _VALUE, _ENUM_ID suffixes. ORM methods return a different structure. Code processing the result must be adapted.

Transactions. The old API did not always wrap operations in transactions. D7 provides explicit transactions:

$connection = \Bitrix\Main\Application::getConnection();
$connection->startTransaction();
try {
    // multiple operations
    $connection->commitTransaction();
} catch (\Throwable $e) {
    $connection->rollbackTransaction();
    throw $e;
}

How do we guarantee quality?

We are certified 1C-Bitrix specialists with over 5 years of experience and more than 50 completed refactoring projects. We use style guides and automated testing. We provide a code warranty — if bugs are found due to our fault, we fix them free of charge within a month.

What to refactor first

Timelines

Refactoring is technical debt that you pay now to avoid paying three times more in a year. Code on the old API does not become more reliable over time — with every Bitrix update, the risk of incompatibility grows. Get a consultation and project assessment — contact us for a detailed commercial proposal with a work plan.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.