Migrate 1C-Bitrix Site with Zero Downtime

Migrate 1C-Bitrix Site with Zero Downtime: Step-by-Step

Moving a Bitrix site is not a routine task—it’s a process with dozens of nuances. Miss one and you’ll get a 500 error, lost orders, or broken images. In 10 years we’ve conducted over 50 migrations and know every pitfall: hardcoded paths, license binding to server bind-name, hidden caches. We guarantee zero downtime when properly organized. Time and cost savings compared to self-transfer can reach 40%. For example, we recently moved an online store with 50,000 products and 1C integration—the entire process took 4 hours with zero downtime. Professional migration is 10 times faster and 5 times more reliable. Get a project assessment—we’ll calculate the timeline and cost individually. More about the DNS protocol can be found on Wikipedia. 1C-Bitrix documentation recommends lowering TTL to 300 seconds 24–48 hours before the transfer: "When changing DNS, it is important to reduce the record's time to live in advance."

Where Paths and Settings Are Hardcoded — Safe Site Transfer

Before migration, know the critical data storage points:

• /bitrix/.settings.php — database connection, host, port, db name
• /bitrix/php_interface/dbconn.php — legacy kernel (if still used)
• In DB table b_lang — domain bound to site
• /bitrix/cache/ and /bitrix/managed_cache/ — cache to clear
• /upload/ — media files, sometimes tens of GB
• License key — bound to domain and server

Why Cache Must Be Cleared After Migration

After transfer, old cache contains references to the old server. If not removed, the site will try to load resources from a non‑existent address. Cache clearing is mandatory, done both via admin panel and directly via command.

Step-by-Step Migration Process

1. Prepare the new server. It must meet Bitrix requirements: correct PHP version (for v22+ — PHP 8.0–8.2), extensions (mbstring, curl, gd, zip, xml, json), web server with proper rewrite rules. Copy .htaccess or nginx config with the site—they may have custom rules.

2. Backup files

   tar -czf /tmp/site-backup.tar.gz \ --exclude='./bitrix/cache' \ --exclude='./bitrix/managed_cache' \ --exclude='./bitrix/stack_cache' \ /var/www/html/ 

   Transfer /upload/ separately due to large size. Database dump

   mysqldump -u bitrix_user -p bitrix_db \ --single-transaction \ --routines \ --triggers \ > /tmp/bitrix_db.sql 

   The --single-transaction flag is critical for InnoDB—it ensures a consistent snapshot without locks.

   Deploy on new server Unpack the file archive and import the database:

   mysql -u bitrix_user -p bitrix_db < /tmp/bitrix_db.sql 

   Update configuration /bitrix/.settings.php — update database connection parameters:

   return [ 'connections' => [ 'value' => [ 'default' => [ 'className' => '\Bitrix\Main\DB\MysqlCommonConnection', 'host' => 'localhost', 'database' => 'bitrix_db', 'login' => 'bitrix_user', 'password' => 'new_password', 'options' => 2, ], ], ], ]; 

   Change domain in database

   UPDATE b_lang SET SERVER_NAME = 'newdomain.ru' WHERE LID = 's1'; 

   Also check b_option and b_iblock for hardcoded URLs.

   License key After migration, reattach the key in the admin panel (Settings → License). If the server changed, you may need to contact 1C-Bitrix support.

   Clear cache Delete cache folders on the server: rm -rf /var/www/html/bitrix/cache/* /var/www/html/bitrix/managed_cache/* /var/www/html/bitrix/stack_cache/*. Also clear cache in admin panel: Settings → Performance → Clear cache.

   Additional tips

   Check permissions on `/upload/` (usually 755) and owner (www-data). Ensure crontab jobs are copied and paths updated.

   Main Risks of Self-Migration

   Often forgotten: updating the domain in b_option or clearing style cache—the site looks broken. For e-commerce it’s critical: during DNS switch, orders may go to both servers. We solve this by parallel operation and 301 redirect on the old server.

   How to Test the Site After Migration?

   Test using the hosts file (without changing DNS): 111.222.333.444 olddomain.ru Checklist:

   • Homepage loads
   • Catalog and product pages
   • Cart and checkout
   • Personal account
   • Admin panel
   • HTTPS — certificate installed
   • Product images
   • Email notifications

   Timelines

   Site scale	Migration time
   Small site (up to 10 GB, simple DB)	4–8 hours
   Medium store (10–50 GB)	1–2 days
   Large portal (50+ GB, complex integrations)	2–5 days

   Comparison: Self-Migration vs Professional

   Criterion	Self-migration	With us
   Preparation time	2–4 hours reading docs	15 minutes consultation
   Error risk	High (missed paths, cache)	Minimal (checklist, experience)
   Site downtime	Several hours to a day	Zero or 15–30 minutes
   Result guarantee	No	14 days free support
   Budget savings	—	Up to 40% by eliminating errors

   What's Included in Our Migration Service

   • Audit of current architecture and identifying hidden bindings
   • New server preparation to Bitrix requirements
   • File and database transfer preserving structure
   • Update all configurations and license key
   • Cache clearing and testing per checklist
   • Help with DNS switching and 301 redirects
   • Admin training and final documentation

   Our team has 10+ years of Bitrix experience and has conducted over 50 migrations. Get a migration consultation — contact us. Request a project assessment — we will calculate timeline and cost individually.