Implementing a new CRM can be a real challenge for any business, especially when it comes to switching from one system to another.
Using the case of StickPeek , a manufacturer of corporate merch, as an example, we show how to switch from amoCRM to Bitrix24 as painlessly and effectively as possible. Yulia Pyankova, head of the CRM and Integrations unit at Completo , helps with this .
Spoiler : the main goal of this article is to provide practical recommendations and insights that will help you avoid common and not so common mistakes when implementing CRM.
Determining starting positions
Both the initial implementation of CRM and the change of the system used are necessary to achieve specific goals.
To make this happen, you need to assess your sales directors email lists starting positions as objectively as possible and identify the tasks that need to be completed.
In this example, the Client decided to switch from amoCRM to Bitrix24, seeking to unite their sales and production departments in one system to increase efficiency. And the Completo team provided support to ensure the transition went linking keywords to a long string as smoothly as possible.
Next, we will examine in detail each stage of implementing a new CRM system, and then draw conclusions about the mistakes made and give recommendations on how to avoid similar ones.
Stage 1. Setting tasks
At the start of a project, it is vital to clearly formulate the objectives.
For StickPeek these were:
1. unification of sales and production departments in one program to optimize processes
The company’s sales team used amoCRM to manage clients and deals, while the production team managed projects, tasks, and archives in Wrike.
Consolidation of department work in one system (Bitrix24) was necessary to achieve greater coherence and integration of processes.
2. transferring data about clients, companies and transactions from AmoCRM to Bitrix24 without losing information
It was important to transfer everything related to transactions and clients, including data on companies and contacts, and in existing vietnam data transactions to preserve the fields and interaction history so that managers could continue working without losing information.
There was a lot of work to be done. Image from the author’s archive
3. Transferring current and archived production projects from Wrike to Bitrix24 while maintaining the structure
It was necessary to “drag and drop” not only active projects, but also historical data, including tasks, attached files, and comments from employees.
Moreover, maintaining the project management structure adopted in the production department was critical to ensuring continuity of work.
We, of course, took this into account and the distribution of tasks:
- allowed us to develop a clear plan of action;
- helped to set priorities and focus on key aspects of implementation.