Companies cramped inside a pipeline
amoCRM is strong at sales and weak where delivery begins after the sale: projects, stages, sub-tasks, documents.
Migration
Migration from amoCRM to Planfix
We move contacts, deals and correspondence out of amoCRM and add what was missing there: tasks, projects, documents and granular permissions.
- Contacts, deals, notes, communication history
- Tasks and projects, not just pipelines
- Dropping Russian software without losing the database
Free consultation
Who the switch to Planfix fits
Service and project businesses
When client work runs for months instead of closing a deal and moving on.
Those dropping Russian software
A switch that preserves the whole client base and communication history.
Multi-department teams
Different roles see different things — Planfix permissions are far more granular.
What does not migrate automatically — and what we do about it
This is the part commercial proposals stay quiet about. Data almost always moves; the working logic never moves by itself.
Business processes, robots and triggers
Automations have no common format across systems, so they have to be rebuilt. We inventory the live automations in the old system and reassemble the ones that matter on the new platform.
Access rights and roles
Every CRM models permissions differently. We port the meaning — who should see what — not a mechanical copy of settings.
Reports and dashboards
They are rebuilt for the new data structure. Usually that is an improvement: most legacy reports had not been opened in years.
Third-party marketplace apps
Replaced by native features of the new system or by n8n scenarios. We list them during the audit — this is exactly where the unpleasant surprises hide after the shutdown.
Raw technical logs
Service records are not migrated: they carry no value outside the old system and only bloat the new database.
How the migration goes
1. Audit of the old system
We count the real volumes: contacts, deals, tasks, files, which pipelines are alive and which are abandoned. An estimate without those numbers is impossible — this is where multiples hide.
2. Field map and the scope decision
We put in writing what moves and what stays in the archive. Moving everything "just in case" is the most expensive and least useful option.
3. Trial migration and reconciliation
We load a subset, reconcile counts and control fields, and show you the result. Only then does the full transfer start.
4. Full migration and parallel run
Everything moves, both systems run side by side for a few days so the team adapts. Then the old one is switched off and you get the reconciliation protocol.
What we migrate
From amoCRM the whole active asset usually moves: base, deals and correspondence. The only question is how deep to pull the history.
Contacts and companiesDeals across pipelinesNotes and historyTasksFilesUsers
amoCRM → Planfix switch
Roughly 2–6 weeks
- Audit of the database and processes
- Field map and migration boundary
- Trial transfer with reconciliation
- Post-sale processes built out (tasks, projects)
- Roles and permissions setup
- Team training
Frequently asked questions
Can email and messenger correspondence be moved?
Yes, communication history moves into client cards. Live channels (mail, messengers, telephony) are connected to Planfix separately so new conversations are logged there.
We have many fields on the deal card. Is that a problem?
No. But at the audit we usually find that some of them have been empty for years. Moving those multiplies the mess; we decide on each field together and put it in writing.
How long does a migration take?
A typical SMB project runs from two weeks to about six weeks. The timeline is driven not by data volume but by how many processes have to be rebuilt and how fast decisions come from your side.
Can we keep working during the switch?
Yes. The old system stays live until cut-over, and both run in parallel for a few days. We agree on a freeze point separately — after it new data goes only into the new CRM.
What if something turns out to be missing afterwards?
We do not delete the old system and we leave a full data export in files. You keep access to the archive even after the old subscription expires.
How much does it cost?
There is no fixed price list: the cost depends on data volume, the number of pipelines and the processes to rebuild. We calculate it individually after the audit — which is why the audit comes first and costs you nothing.
Related case studies
Case: Complex Migration of an Engineering Company from Bitrix24 to Planfix
How we migrated 40+ active users, 13 business processes, and the entire historical database from Bitrix24 to Planfix, transforming a CRM into a full-fledged ERP system.
Read more →Case: How We Automated a Law Firm with Planfix and Make.com
Learn how automating document generation and task management allowed a law firm to reduce routine time by 80% and gain full control over cases.
Read more →