Mikhail Filippov

Bitrix24 migration: Cloud-to-self-hosted

Advantages of the cloud version of Bitrix24

The main advantage of the cloud version of Bitrix24 is that you only need to register on Bitrix24.com with an email account or your social media accounts to have your own portal. That's it!
Everything related to the support and development of the portal is provided by the supplier - Bitrix24.


In addition, Bitrix24 provides access security and storage. 

For the on-premise version, you only get a license key. However, you must install the solution yourself.
You will also need to provide yourself with a server. From now you will also have to do technical support by yourself.

The Cloud version has limited abilities for configuration and modification. 

Oftentimes, businesses need more functions than those provided, and can get these extra features by installing extensions from the B24 Marketplace. 

If your company has needs which can’t be fulfilled by the Marketplace apps, it's time to consider migrating to the on-premise B24.

 

Advantages of on-premise edition Bitrix24

  1. Access to the administrative panel with many settings.

  2. Access to the server with the program itself and the database.

  3. Access to the API, which allows you to integrate Bitrix24 with other systems.

  4. Open source code that allows you to customize the system according to your individual requirements.

The ability to modify and integrate with other systems is the main reason why several of our clients choose the on-premise edition of Bitrix24  or migrate from cloud version to the on-premise version.

 

How to know when it is time to migrate

It's time to seriously consider moving from the cloud to the on-premise edition, if you need to:

  1. Customize interface and Business logic.

  2. Change the appearance and location of menus, widgets and other items.

  3. Integrate Bitrix24 with any third-party programs, such as Accounting Systems, Oracle ERP, MS Exchange Server, Active Directory (AD / LDAP), Asterisk and others.

  4. Ensure data storage on the company’s internal servers.

  5. Have backup copies of the portal in case a data recovery is needed.

  6. Create new modules with the necessary functionality.

  7. Create complex Business processes that have a user-friendly interface.

 

Steps for Migration

So, you’ve decided to migrate. What next?


1. Purchase a license key. 

To get acquainted with the cost of the on-premise edition and the differences between the editions, you can go to the PRICES section on Bitrix24 official website.

After acquiring the license, you need to register the key. Migration is possible only with an active commercial key. 

You can purchase a license key through INTERVOLGARU.


When you request a B24 Implementation from us, we will purchase the key, install B24 on your private server and make necessary configurations.

We'll save you time and avoid risks.


The information on the activated key looks like this:




2.  Create a domain name for the portal and bind it to the IP address of the server where it will be located. 

That is, we assign the A-record to the portal domain. Typically, the portal uses a subdomain to the main site. For example, if the site domain is example.com, then for the portal we create a subdomain called crm.example.com or portal.example.com.


3. Selection and preparation of the server for on-premise edition

Before B24’s technical support will give you a backup copy of your cloud portal, you need to prepare a server on which the on-premise version will be deployed. The server can be hosted by your company or a hosting provider.

We recommend using the second option and not buying a separate server. Cloud hosting is a fairly reliable and inexpensive platform for allocating resources. The main advantages of a cloud server are:

  • the cost of operation for cloud hosting is often lower, you pay only for the resources used;

  • scalability - you can easily increase RAM and disk space;

  • data protection and recovery - all data in the cloud is securely protected and recovery is provided by automatic backup of information to an adjacent server;

Requirements for deploying an on-premise B24

The hardware requirements are calculated individually, based on your activities and the number of active users in the portal. To deploy a small portal, you need:

  • an SSD hard drive with a minimum capacity of 100 GB;

  • 8GB RAM or more;

  • Intel Core i7 processor or better.

For the portal to work optimally, it is recommended to install the "Bitrix Environment" package. Also, as a server software, you can use the BitrixVM virtual machine environment.

You also need to make sure that your web-server has at least three times more space on disk than the size of the backup.

 

4. Contact Technical Support

To transfer your cloud data to the self-hosted version of Bitrix24, you need to make a request to Bitrix24 technical support. You can contact them via the Bitrix24 website or via chat in your portal. You should send them the following data:

  1. The license key with the number of users is not less than the number of users in your portal in Bitrix24. If you purchased a license for additional users, you will also need a coupon for additional users.

  2. The name of your portal in Bitrix24.

  3. Authorization data (login and password) of the user who created your cloud portal on Bitrix24.

  4. The date stamp of the backup -(the last day of portal work in the cloud version).

  5. Acknowledgment that you have read and agree with the terms of portal migration.

After you have sent this information, you will need to coordinate the date  when they can prepare the backup (A specialist will tell you the nearest suitable date). 

Backup preparation takes from one to five working days, depending on the amount of your data in the cloud.

Specialists can make the backup only during work hours (Mon - Fri from 10:00am  to 7:00 pm Moscow time). So, please have this in mind.

While B24 is preparing the backup, it is not advisable to use the portal because all newly entered data can be lost. Backup will be done ONLY ONCE, so it's important to prepare your portal in advance, before the agreed date for backup.

Bitrix24 uses amazon.com servers for cloud portals, so, the data transfer rate became lower than it was before.
Daytime 5-6 Mb/s, and at night falls to 400 Kb/s. But it also depends a lot on what region your server is in.


 

5. Deploying the on-premise edition on the server

When you get your backup from B24 technical support, you need to deploy it on the selected hosting server. 

At the end of this process, you get an exact copy of your Bitrix24 portal with all the data. The administration panel will also appear in the portal web interface. For authorization use the login and password of the account on the Bitrix24 portal.

 

Could it really be that simple?  buy a license, activate it, request a backup from 1C-Bitrix support, and deploy it on our server, that’s all?
Of course Not.
There are many nuances to put into consideration and many possible problems that could arise.


Points to consider / problems during migration


1. Migrating portal users

The most common problem is the migration of user accounts for the portal. After migration from cloud to on-premise, users will not be able to log in with their old password. There are two ways to solve the problem - you can use the password recovery form in the portal or the administrator must manually reset the passwords of such users.

 

2. Troubles with extranet users

It is known that extranet users will be disabled after portal migration. The problem is solved by reinstalling the extranet site on the on-premise version. But sometimes there can be errors such as:

  • extranet users can not being able to send posts to the "Activity Stream", inability to use chats and tasks;

  • extranet users being only able to view what’s happening in the portal. 

  • extranet users can receive messages, but can not send them.

In this case, contact Bitrix24 support.




3. How to migrate telephony

Another task that arises after migration from cloud to on-premise is the migration of telephony. If an office PBX has been connected to the cloud portal, this account must be moved from the cloud to the hosted version separately.

Basic steps:

  • write to the technical support service Bitrix24 with a request to migrate the PBX account;

  • send the contracts and documents for connecting telephony(for example for Asterisk, Mango, Comagic) to Bitrix24 technical support;

  • For telephony and notifications to work correctly in the portal, you must install a  valid SSL certificate.

 

4. Cloud applications - a new installation

It is generally known that after migration,some applications that were installed in the cloud version do not work. You need to reinstall them. And sometimes not all applications work even after reinstallation.

For example, "Document Generator". You may need to additionally reconfigure document enumerators, set access rights for employees, assign access rights to document templates, etc.

Bitrix24 has changed a lot lately. It has become more complex, which  makes it better,  but also more difficult to configure, leading to additional problems when migrating your portal to your private server.

 

5. What other surprises may arise

Over the first couple of days, you may experience one of more of these errors:

  • Comments on tasks may not appear completely.

  • You may not be able to create a task from an email.

  • Chatbots may crash.

  • Users may find themselves logged out frequently

  • If there are absolute links to documents in business processes, it will be necessary to correct business processes.

  • The structure of the menu in the cloud and self-hosted portal may not be exactly the same.  In this case, you need to go to the portal structure settings and change them to what users are used to.

  • Some commands in the list of items may not work, for example, "Copy".

  • Opening documents via Google Docs may not work. You need to create and configure a separate Google Docs account for self-hosted Bitrix24.

  • Problems with the mobile application module.

  • Setting tasks and sending messages in "Activity Stream" - you need to configure the domain and add an MX-record.

  • It is also necessary to configure a backup settings and proactive protection against hacker attacks.

Migration of a portal can take anywhere from 2 to 7 days. Downloading a 400 GB portal from the amazon.com data center, where the Bitrix24 cloud is located, can take up to 2 days.

We recommend a Portal audit before migration. This involves an analysis of all functions, applications, business processes that employees use in the portal. This will allow you to highlight the most important functionalities and focus on them first.

Solving these tasks is not easy even for an experienced administrator. There are many nuances and subtleties in the work of Bitrix24. Our specialists can perform the entire complex of tasks for migrating, setting up and launching a self-hosted portal.

 

Conclusion

Having not only smooth, but also challenging experiences, we understand much more deeply the difficulties of migration of the Bitrix24 portal. We have acquired skills that will help you avoid making mistakes.

 

Fill the form below to request a Bitrix24 migration and our sales team will contact you.

  • 25.05.2021