How to update the old Bitrix?

Question

1C-Bitrix

Is it possible to roll up updates after purchasing a "license renewal" from Business + AD / LDAP, Bitrix 14.0.15 to Small Business of the latest version?
Or is it easier to reinstall and roll content?

Answer 1

I tell you how I updated from 14 Business to 18 small business - Bitrix with the transition to php7 and Maria10.
---
1. Entered a new key, but did not update. Made a backup and deployed it to another server with the same configuration.
2. Carried out checks for kernel modification.
3. Changed the encoding from 1251 to utf 8 through a script
4. Started the update
5. Partially updated and crashed with an error on the php version
6. Raised php to version 7.3
7. Continued the update
8. Crashed again, because it was necessary to rescan, reconvert the store , discounts, deliveries....
9. Then launched the update again
10. Raised the muscle version from 5 to 10
11. Made a backup copy and deployed it on the production server
12. There were no global edits. In some places, only replaced obsolete functions.
During the update, Bitrix cursed modules that were not included in the license. But we didn't use them anyway. Removed.
Everything is working. By the time it took about 20 hours. Most of the time was taken by packaging, unpacking, downloading, uploading archives.

Answer 2

It is important to consider what customizations have been performed on the site since the last update and the readiness of the site's custom code to switch to another version of php, since the current version of Bitrix requires the current version of php.
Procedure and things to consider:
1. Activate the license on the main version of the site without installing updates.
2. Deploy a test copy of the site on the site with the settings corresponding to the main site
. 3. Check the "Quality Monitor" for modification of the Bitrix core files.
3.1. If modifications are found, check that this is a custom code that is needed for the project to work and written in an invalid place or a false positive of the site verification tools.
3.2. Move the identified custom code to the correct place - separate components or handler files where this code will not be overwritten during the update.
4. On a test copy, upgrade to 17.1 or 17.5. At this stage, the first difficulties can be identified.
4.1. The checkout components are moving to the new API, and if there are custom handlers in the checkout templates, errors will be detected.
4.2. Serious changes in working with JS Bitrix also need to check the readiness of the site to work with the new JS
4.3. If the site is running on php 5.4, it's time to transfer the work to php 5.6
5. Convert the database tables of the online store and switch to the D7 core.
6. Most likely there will be problems in the checkout functionality. You can temporarily switch checkout to legacy API compatibility mode.
7. If 1C was connected to the site, payment services, delivery services - at this stage they will be abandoned, since the format of Bitrix with payments has changed.
8. If everything works, update Bitrix to 18.1 and check the functionality
9. Switch the site to php 7.0 (you can immediately to php 7.1, but it is better to solve problems in stages)
10. After switching the php version, check the correctness of the custom code on the new version and, if necessary rewrite the code to compatible with the current version of php
This is a common scenario. Each case is individual and the labor costs for the task depend on the quality of the site development, the quality of the custom code. But even with correct development, with such a significant update, many third-party modules installed on the site will require further development or at least an update.
The task can require from 10 hours. up to 200 hours or more. It depends on the quantity and quality of the custom code (on the size of the project's technology debt). In some cases, all the "crutch" custom code comes to be processed into modules and components.
The most neglected case that I have met is a technological debt of 500-600 hours.
it was decided to launch a new project and gradually implement all custom functionality correctly in it without losing the ability to install updates.
Do not launch your projects - make sure that the technical specialists, when performing the task, comply with the Bitrix requirements for implementations and retain the ability to install updates.

Answer 3

make a copy of the site and try updating.
content for the store is not very easy to roll (products, pictures, orders, users)

Answer 4

I updated after 3 years (I bought an extension), the update got up fine!
But I made a backup first...