Should I switch to 1s fresh?

Question

1C-Bitrix

A site in bitre, written-rewritten over the years by different developers.
Platform 1c, conf UPP, a lot was also written. Own servers with RDS and MSSQL. 20 users.
10000 items.
There was a desire to do everything from scratch. Make a clean installation of the beater, transfer the products and all their characteristics and so on to a new installation.
1c also deploy complex automation from scratch.
In both operations, adhere to the stock code as much as possible, that is, in 1s, the entire nomenclature will be created by a standard import tool (xml, it seems there).
And then the question is, isn't it better to abandon your server and switch to fresh? What potential problems can arise at the interface of the 1sfresh exchange <--> website?

Answer 1

Complex in fresh is available only at the CORP tariff for at least 10 users at once for 67 thousand rubles. in year. + there is a closed configurator in fresh, you can customize it only with the help of extensions, processing and external forms, and the configuration code itself is not available.

Answer 2

And then the question is, isn't it better to abandon your server and switch to fresh? What potential problems can arise at the interface of the 1sfresh exchange <--> website?

Before I left the franchise, I managed to see how they took clients to the cloud with a bundle with Bitrix. You simply shift the responsibility for the performance of the exchange from your admin to the cloud admins.

Answer 3

Working in the fresh service:
1. You don't need your own servers, you don't need to update the configuration yourself when new versions are released. This work is undertaken by the service provider.
2. Restriction on customization. It can be modified only with the help of extensions or additional reports and processing. Plus, it is necessary that your revision be audited by the service provider.
3. Limiting the possibilities of investigating the behavior of the program when setting up integration (debugging, collecting logs, etc.)
Local database:
1. You must have your own server and install updates yourself.
2. It is possible to cut the configuration as you like (considering that the more it is cut, the more difficult it is to update)
3. You can use almost any means of investigating behavior.
That is, if you stick to the position of working with the most typical code, you save on servers, update time and, as a bonus, you get access from anywhere where there is Internet. However, in terms of integration with external systems, the investigation of problems may be longer than when working with an on-premises solution, due to the need to involve the service provider's specialists in the investigation.