amoCRM and GDPR · Romania

You cannot say where your database sits. Under GDPR that is a problem.

GDPR sets strict rules on transferring data outside the European Union, and Romania has applied them since 2018. amoCRM stores data in Russia, which the EU does not recognise as a country with an adequate level of protection. Kommo does not disclose its storage region at all: its policy reserves the right to keep data «anywhere in the world, including the USA».

What the law requires

It is not a matter of convenience, it is one of liability

Transferring data outside the EU is regulated

A separate chapter of GDPR sets out when data may be transferred outside the European Union: under an adequacy decision, under appropriate safeguards, or in the cases listed explicitly.

It is not the vendor who answers, it is you

The controller of your customers’ personal data is your company. The questions will go to it, not to the CRM’s developer.

The problem is not the quality of amoCRM

The system itself is decent and we have worked with it. The question is purely where the database physically sits and whether there are grounds to send it there.

A decision has to be made

Three options, and one of them is to do nothing

Stay on amoCRM risky

You will have to prove the transfer is lawful yourself: obtain a data processing agreement, standard contractual clauses and a list of sub-processors from the vendor, then assess the transfer risks. Kommo publishes none of this — you will have to request it. It is the controller who answers to the regulator, that is you, not the vendor.

Move to Bitrix24 what we suggest

The cloud with a data centre in Frankfurt, or the on-premise version on your own server. Functionally the system covers the same ground and more, and the hosting question disappears entirely.

Look for another system

A workable option if you find a suitable one hosted in the EU or at your premises. We will say honestly if Bitrix24 is overkill for your task — moving for the sake of moving makes no sense.

A detailed breakdown of the two Bitrix24 hosting options — the cloud with data in Frankfurt and the on-premise version on your own server — is on the Bitrix24 page.

What we move

Everything the sales team works with every day

Deals

With every field, amount, date and the current stage.

Contacts and companies

Together with the links between them and the history of interactions.

Message history

Emails and messages, attached to the right deals and contacts.

Tasks and notes

Including the open ones — so the team does not lose work in progress.

Files

Contracts, invoices and quotes from the cards.

Deal stages and automations

We recreate the logic: stages, access rights, automatic actions and notifications.

How the move goes

Five steps, and sales never stop

01

We look at what you have

We export the structure: which stages, fields, automations and integrations are actually used. Some of them usually turn out to be dead — there is no point moving those.

02

We build the new system

We configure Bitrix24 around your processes. We do not copy amoCRM one to one: whatever was a workaround gets fixed at this step.

03

We migrate the data

First a trial migration onto a copy, and we reconcile the numbers. Only then the real one.

04

We switch over and train

We run both systems side by side for a while so nothing is lost. We show the team where everything lives.

05

We keep supporting

Small things always surface in the first weeks. We answer and fix them.

Honestly

What will still be unpleasant about the move

  • The interface is different. Bitrix24 is denser and at first glance harder than amoCRM — the team will grumble for the first weeks, that is normal and it passes.
  • Some custom development will have to be rebuilt rather than moved. Sometimes that is for the better, but it is work.
  • A perfect migration of message history does not exist: something will land in the wrong card. We check it on the trial run, but promising 100 % would be a lie.

We say this upfront so that it is not a surprise a month later. If the review shows it is too early for you to move, we will say so.

One step

A review of the move — 30 minutes

We will look at what you have configured in amoCRM, estimate the scope of the migration and name the timings. We will say plainly if some automations are easier to rebuild from scratch.

What happens next

  1. We call you back during working hoursUsually within an hour. If it is awkward to talk — we write instead.
  2. We ask a few questionsWhat you have now, what does not work, which numbers you count as a result.
  3. We tell you straightWhat is worth doing first, how long it takes and whether you need us at all.

By pressing the button you agree to your phone number being processed so we can reply — how we handle data.

Would rather not leave your number — call us: +40 764 671 177 We answer during working hours.