In this case, you will learn how we solved a non-trivial IT task for a large media Without noise and dust company doing business in 19 cities in Russia. Why the move was necessary, what we loaded, where we “took” and why we parted with the hard-earned assets. And most importantly, how we ended up with a CRM greece telegram data system even better than the previous one on an updated, working portal. And not a single advertiser (or rather, data about them) suffered.
- Our client and his goals
- What tasks did the client set for us?
- Merge versions of Bitrix24: best practices
- It is impossible to finalize or update. Where to put the comma?
- The difficulties of transferring. The solution that did not work
- Changing portals. In white gloves
- Results and Prospects
Our client and his goals
In September 2022, the Vyberi Radio group of companies, the largest regional Without noise and dust radio holding within the federal MEDIA1 group, approached us at IPG. Currently, the structure of Vyberi Radio includes 123 radio stations in 19 cities of Russia, 650 employees and 8.2 million listeners. The company organizes broadcasting, air programming and sales of advertising opportunities for radio stations in order to promote advertisers’ brands.
Since 2006, the business has been developing features and benefits of having it in your company steadily, growing in. Assets (last year, Vyberi Radio was transferr to the management of Gazprom-Media Radio stations in Perm, Yekaterinburg and Samara). With the. Growth of the business, staff and client base, the management company had a need to. Receive more analytics from CRM.
GKVR already had a CRM on Bitrix, the previous contractor implement a corporate portal here bas on the box Bitrix24 in the Enterprise edition (for large companies). At the same time, 300 managers from different cities are currently working with the Bitrix24 functionality. At this stage, “Choose Radio” requir the development of a new system and customization of Bitrix24 to the needs of the company.
The customer was recommend us (IPG) by the vendor (1C-Bitrix) as experienced integrators. We were lucky enough to take part in the project with the aim of completing the tasks that the previous contractor had difficulties with.
What tasks did the client set for us?
Since we need to pick up the workflow for developing the product after another integrator, the first thing we did was audit the work done on the box version of 1C-Bitrix24 “Choose Radio”. Namely: we analyz the code, determined what work had already been done by the taiwan data previous contractor (in terms of building business processes and setting up CRM), audited the integration with 1C for transferring orders and the client base, identified errors and issu recommendations for improvements. We drew up and agre on a work plan for the project.
The main problem was that the old GKVR portal, where the company’s entire client base was stor , at some point stopp updating “without problems”, and the customer could no longer keep it up to date. The reason was that there were too many improvements with core customization, which led to an error updating Bitrix.
In this regard, the customer decided to move to a new portal , where our predecessors-integrators actually carried out the work. And the task of our specialists was to transfer the customer’s entire client base (including transactions, invoices, documents, contacts, history of interaction with clients and other CRM modules) from the old Bitrix24 portal to the new one.
In other words, it was necessary to find a solution on how to organize such a move. In a short time, seamlessly, without data loss. By creating a convenient and functional product that would unite all interactions between managers and clients into one working system.
We had a lot of work ahead of us.
Merge versions of Bitrix24: best practices
The transfer of the client base to the new portal (contacts to contacts, companies to companies, deals to deals) is a standard, uncomplicated process. In the case of “Choose Radio”, we were dealing with two different versions of Bitrix24 : the old portal had not been updated since 2018 and, in fact, had already outlived its usefulness, and the new one (to which we were moving) was updated to the state of 2022. It is quite difficult to merge product versions, crossing the functionality of the old and new portals, without losing data and subsequent conflicts and errors in the system.
For example, we had to transfer data from the CRM “Leads” section (on the old portal) to a completely new logic – to the Smart Processes section (on the new portal). This was a certain challenge (we will explain why soon), but we coped with it.
In addition to the entities themselves (leads, contacts, companies, deals), it was necessary to transfer the entire history of interactions with clients (phone calls, letters, comments, tasks, etc.).
In addition, the task was complicated by the fact that it was necessary to transfer information from customized user fields of various entities of the old portal to the standard fields of the new portal, because the functionality required by the client and previously improved appeared in the latest version of Bitrix.Taiwan Lists
