The reason companies stay on a CRM that no longer serves them is almost always the same: fear of losing data in the move. It is a well-founded fear, because a badly done import duplicates clients, corrupts special characters and mixes up pipeline stages. Zarina CRM brings data in from a file exported from the old system, matches the columns on its own, shows you what will go in before it goes in, flags matches with what you already have and, for operational imports, lets you undo the whole operation.
There is no magic button. There is a short path in which every step can be stopped before it breaks anything.
Export the data from the old system to CSV or Excel. Any serious CRM has an export; if yours does not, we help you get the data out of the database.
The file goes into the application. xlsx, csv, txt and tsv are accepted, up to 10 MB per file.
The application recognises common column headers on its own and proposes the mapping. Whatever it misses, you correct from the list.
You see what will go in, row by row, with errors marked and matches with the existing database flagged. Nothing has been written yet.
Only what you confirmed runs. The import is logged with the date, the user and the number of rows.
You check a sample in the application. For operational imports, if it is not right, the whole import is undone.
There is no single universal import, because a client, a lead and a supplier are not checked the same way. Each has its own logic.
Companies and individuals, with tax details, contacts and assigned owner. Conversion to the correct encoding happens on reading, so special characters are not corrupted.
Opportunities with the stage they are in, value, probability and the source they came from. The pipeline is not flattened on import.
Suppliers, expenses, cash transactions, equipment and projects. Here there is an import history and undo.
The application knows the ways columns are usually named, in English and Romanian, and matches them to its own fields.
The preview step is not a summary. It is the actual list of rows, with problems marked on each.
Rows repeated in the uploaded file are flagged by the keys that identify the record, not by the whole row.
If a record in the file resembles one you already have, it is shown before the import, not after.
Rows with missing data or the wrong format are marked individually, with the reason. The rest of the file is not blocked by them.
It is the difference between an import you try calmly and one you dread.
The part other vendors leave until after the signature.
We have seen them with clients who came to us after a rushed migration.
The export comes in a different encoding than the import expects, and half the names end up with symbols instead of letters. It is noticed two weeks later, when someone searches for a client and cannot find them.
Conversion to the correct encoding happens when the file is read, before any matching.
The import is run twice, because the first time it “did not work”. Now the database has every client twice, and reports show double.
Matches with existing records are shown before the import, not after.
All leads go into the first stage, with no value and no probability, because the import did not know what to do with those columns. The sales forecast becomes useless.
Stage, value, probability and source have their own fields on import.
You send us the export from the old system and we tell you what can be moved, what cannot and where the problems in the data are, before any import.
We run it first on a test installation, check the result together and only then import into the live installation.
We check a sample of clients, leads and documents together, and only then consider the migration complete. Details are on the implementation page.
Companies paying monthly for a cloud CRM, with a few thousand clients already in it, that want to move to a lifetime licence without starting from zero.
Companies that have kept records in Excel for years and need those files to end up in a system, not in the bin.
Anyone who needs permanent two-way sync between Zarina CRM and another system. That is an integration, not a migration, and is discussed separately.
A client export is a database of people. It deserves a clear question and a short answer.
From any that allows export to CSV or Excel — in practice, all of them. It does not matter which system you had before; what matters is the columns in the exported file. There is no direct connector to any particular CRM.
xlsx, csv, txt and tsv, up to 10 MB per file. A larger database is split into several files and imported one by one.
No. The file is converted to the correct encoding when read, before columns are matched. It is the most common import problem and is handled from the start.
In the preview you will see the matches with records you already have, before anything is written. For operational imports, if it happened anyway, the import can be undone.
Yes. The lead import has fields for stage, value, currency, probability of winning and source. The pipeline does not end up flattened in the first column.
Usually not. The call log, emails and notes from the other system have no structural equivalent we could fill in correctly. They can be attached as a document to the client, if the export contains them.
It depends almost entirely on how clean the data is, not on volume. A clean export of a few thousand clients is imported the same day. An export with duplicates and mixed-up columns needs cleaning first.
Yes. Ask for demo access and upload a file with a few dozen rows from your database. You see exactly how matching and preview look, on your own data.
You can do imports yourselves; they are part of the application. If you prefer us to do them, they are part of the implementation; the terms are on the pricing page.
We recommend keeping it active for a month after migration, read-only, until you are sure nothing is missing. Only then close the subscription.
What happens from signature to the first working day, including data migration.
Where the data ends up after migration: on your server, not with us.
If your old system has fields and workflows you want to keep exactly as they are.
The edition that fits your activity, into which the migrated data will go.
If you do not want a move, but a permanent link to another system.
The licence, the packages and what is included in implementation, with no surprises at the end.
Lifetime licence, unlimited users, installed on your server. Send us the export from your current system and we will tell you what can be moved, before any contract.