Migrate from Bitrix Business to Enterprise: Cluster, SLA, Turnkey

Imagine your 1C-Bitrix "Business" online store starts slowing down under peak load—500 concurrent sessions, response time drops to 10 seconds. Clients complain, managers get nervous, and you realize it's time to scale. As a team of certified Bitrix specialists with 7 years of experience and over 100 migrations, we frequently encounter this situation. Migrating to the "Enterprise" edition is not just a key change; it's an architectural overhaul that solves load and fault tolerance issues.

What Makes Enterprise Different from Business

Unlimited sites—Enterprise explicitly allows unlimited domains and sites, a must for holdings and agencies. Unrestricted clustering: full web cluster with multiple web servers behind an nginx load balancer, distributed session storage via memcached or Redis, database replication, dedicated Sphinx search server. Extended caching via \Bitrix\Main\Data\Cache in cluster mode. Role-based model across multiple sites via b_user_site. Priority support with SLA from the vendor. File storage on S3-compatible object stores through the clouds module.

When Is Migration to Enterprise Justified?

Migration becomes justified under at least one of these conditions:

• Peak loads that a single server cannot handle (500-1000 concurrent users)
• High availability requirement: one node failure must not bring the site down
• Dozens of sites managed by one team
• Integration with corporate systems (SAP, large 1C configurations) requiring stability
• Regulatory data storage and backup requirements

Why Enterprise Handles Loads Better

Through clustering, Enterprise distributes traffic across multiple servers, giving a 3-5x performance boost over a single Business node. Cluster cache on memcached reduces database response time, and S3 storage offloads the file system. Consult with an architecture specialist—we offer a free analysis of your current load.

How the Migration to Enterprise Works

1. Cluster infrastructure design. We determine the topology: number of web nodes, load balancer (nginx/HAProxy), DB replication scheme (master+replica), distributed cache.
2. Cluster setup. Configuration in dbconn.php for connecting to slave servers, cluster cache configuration via \Bitrix\Main\Config\Option, session storage.
3. Media file transfer. If moving to S3—upload files from /upload/ to storage, configure CDN, update paths in the database.
4. Search setup. Sphinx or Elasticsearch as external search engine—configure the search module to work with an external index.
5. Load testing. After cluster assembly—load testing (Apache JMeter or similar) to verify balancing and fault tolerance.

Timeline Table by Complexity

'cache' => array(
  'type' => 'memcache',
  'hosts' => array('192.168.1.10:11211'),
  'usecluster' => true,
)

Case Study: Large Retailer Migration

Our client—a federal retailer with 47 regional sites on separate Business licenses, united under a common admin panel through a custom aggregator. Sites periodically crashed during promotions. Task: migrate to a single Enterprise with a cluster architecture.

Architecture after migration:

• 3 web nodes behind an nginx load balancer
• MySQL master + 2 replicas (read queries on replicas)
• Cluster memcached for cache and sessions
• Yandex Object Storage for /upload/ via clouds module
• 47 sites under one license with a single catalog and regional pricing

The work took 6 weeks: design (2 weeks), implementation (3 weeks), load testing and launch (1 week). During the next peak promotion, the site handled the load without degradation—the load balancer distributed traffic across nodes.

What's Included in the Work

• Analysis of current architecture and loads
• Cluster topology design
• Web server, load balancer, and cache setup
• Data migration and storage configuration
• Load testing and optimization
• Documentation and training for your team

Timelines

Migration with cluster infrastructure setup: 4-10 weeks depending on the number of sites, integration complexity, and infrastructure requirements. For simple scenarios (multi-site without cluster): 2-4 weeks.

Order a turnkey migration—we will assess your project and suggest the optimal architecture. Get a consultation for your project: we provide a free load analysis and migration path advice.

How Choosing the Wrong 1C-Bitrix Edition Breaks Your Project

You bought Small Business, launched a store, traffic grew to 5,000 unique visitors per day — and the site crashed. Composite cache is only available in Business, web cluster too. An upgrade costs the difference in license price plus work to configure new modules. Choosing and configuring the right 1C-Bitrix edition upfront saves up to 40% on licensing. It also avoids unplanned upgrade costs — saving on average 15,000–30,000 RUB when upgrading from Small Business to Business in advance instead of urgently. Over 8 years of working with Bitrix, we have performed over 200 upgrades and seen all typical mistakes: from buying Start for a 50,000-product catalog to using Business for a landing page with 100 visits per day. Our principle is to select the edition that matches your real needs and configure it so you do not overpay for unnecessary modules — and also do not hit a ceiling at the first traffic spike.

1C-Bitrix Editions: Site Management

Four editions, and the difference lies not in the number of features but in the available core modules. The official 1C-Bitrix documentation states that composite cache is only available in Business and above.

Start is minimal, only content modules: iblock, form, basic SEO. For business card sites and landing pages. No sale module — cannot build a store.

Standard adds communication: blog, social network, forum, extended tech support. For corporate sites and portals with user-generated content.

Small Business is the first edition with e-commerce: the sale module appears. Comfortable ceiling is up to about 10,000 products without serious optimization. For small stores and catalogs with ordering.

Business is the full set: composite cache (TTFB drops from 800 ms to 50–80 ms — 10–15 times faster), web cluster, multisite, multi-warehouse, REST API. For large stores, marketplaces, projects with 10,000+ visitors per day.

How Does Composite Cache Reduce Server Load?

Composite cache (main.composite) speeds up page loading 10–15 times compared to dynamic generation. For a store with 3,000+ visitors per day, without composite the server starts struggling: average response time increases, database overload, checkout pages time out. Composite solves this radically — HTML is served by nginx without running PHP. It is important to correctly configure exclude masks for cart, personal account, and pages requiring real-time data. We configure this on every upgrade to Business.

1C-Bitrix official documentation: "Composite cache is available only in Business edition and higher."

Avoiding Common Mistakes in Edition Selection

Typical Mistakes

• Buying Start for an online store — no sale module, you either need to upgrade immediately or hack a custom ordering system.
• Choosing Small Business for a project that will grow to 10,000 products in six months — composite cache cannot be enabled, upgrading to Business costs the license difference plus configuration work.
• Using Business for a landing page — overpaying for features that will never be used.

Choosing an Edition for an Online Store

Hard Criteria for Edition Selection

By modules:

• 1C exchange (catalog) → at least Small Business
• Composite cache (main.composite) → only Business
• Web cluster (cluster) → only Business
• Multisite → only Business
• REST API → only Business

By load:

• Up to 1,000 unique visitors/day — any edition can handle
• 1,000–10,000 unique visitors/day — Small Business with nginx/php-fpm tuning hits a ceiling. Business with composite cache is the right choice
• 10,000+ unique visitors/day — only Business with composite and cluster

By budget:

• The price difference between editions is 2-5x
• Upgrade at any time — pay the difference in license cost
• Our principle: take the minimum sufficient. But if you know you will need composite in six months, get Business immediately, because an upgrade also involves configuration work. The total upgrade cost (license difference + setup) typically ranges from 10,000 to 50,000 RUB.

What Happens If You Ignore License Renewal?

An active license provides updates — new versions, security patches, bug fixes, marketplace access, and vendor tech support. When it expires, the site continues to work but remains without updates. For stores this is dangerous — security patches fix vulnerabilities in sale, catalog, main modules. Data leaks from b_sale_order or b_user are just a matter of time. Renewal costs a fraction of buying a new license — typically 20–30% of the full price. Regular renewal is insurance against unpatched CVEs.

Cost Benefits of Planned Edition Upgrades

1C-Bitrix allows upgrading without reinstallation — data is preserved. Process:

1. Pay the difference in license cost
2. Activate new key: Settings → Updates → Registration
3. Install newly available modules via admin panel
4. Configure new functionality
5. Test compatibility

What we do during an upgrade:

• Check custom code for conflicts with new modules — especially custom event handlers like OnBeforeOrderAdd, OnSaleBasketSaved
• Enable and configure composite cache — correct exclude masks for dynamic pages (cart, checkout, personal account)
• Configure multi-warehouse if needed — b_catalog_store, warehouse selection rules
• Run full functional testing on staging
• Document changes

As a result, you get:

• A working site on the new edition with no data loss
• Configured composite cache (if upgraded to Business)
• Testing report and recommendations for further optimization
• Access to staging and documentation of changes

Integrating Site Management with Bitrix24

A common scenario: site on 1C-Bitrix + CRM in Bitrix24. Orders from b_sale_order automatically become leads or deals, unified authorization, client base synchronization. Site forms (form or custom) feed into the CRM funnel. These are two separate licenses and two separate products — integration between them is standard and stable.

Practical Recommendations

• Do not skimp on the edition if you know the functionality will be needed in six months. Upgrading costs the same difference plus configuration and testing.
• Business for projects with growth ambitions — composite cache pays for the price difference at the first traffic spike. Without composite, 3,000+ unique visitors/day will strain the server.
• Bitrix24 and Site Management are different products with different licenses. Confusion here costs money.
• Renew your license annually — renewal is much cheaper than buying a new one, and without updates you risk unpatched CVEs.

What We Offer: Turnkey Selection and Configuration

We do not just consult — we handle the full cycle: analyze your current project, select the edition, purchase the license (if needed), migrate, configure all modules, and train your team. As part of the service, you get:

• An edition selection report with justification
• Migration plan (if upgrading)
• Fully set up staging with the new edition
• Composite cache and cluster configuration (if necessary)
• Documentation of the new configuration
• Guarantee of site functionality after the transition

Contact us today — we can assess your project within one business day and propose the optimal configuration. Receive a personalized cost estimate for selecting and configuring your 1C-Bitrix edition right now.