Migrating records to fresh EspoCRM v10 instance while preserving original record IDs

[partomas]

Hi everyone,

I found that it is possible to migrate CRM records from one EspoCRM system to another while keeping the original record IDs.

In my case, I am planning to migrate to EspoCRM v10 from an existing working system into a fresh new CRM instance. The idea is not to migrate the whole old system with all legacy data and possible “garbage”, but only the required records and configuration.

I would like to understand how EspoCRM generates unique record IDs.

Are there any potential risks or issues if I import records from the old CRM system into a fresh EspoCRM v10 instance while preserving their original IDs? For example, could this cause conflicts with newly created records in the future, or does EspoCRM handle this safely?

I would appreciate any clarification or recommendations regarding this approach.

Thank you.

[yuri]

Hi,

For this case our export import extension is a good choice I believe.

https://docs.espocrm.com/extensions/export-import/overview/

It depends how old is your version. The older it is, the more risk of incompatibility.

[partomas]

Thank you, I'll use it, but I would like to understand how EspoCRM generates unique record IDs.

[yuri]

Preserving IDs should not be a problem.

EspoCRM generates IDs at application level (not DB).

Note that if your version is very old, it's likely the export-import extension will be incompatible with it.

[partomas]

My goal is to migrate only the main data, such as Accounts, Contacts, and some other essential records. I may also move a few lightly customized workflows or reports if needed.

All other logic and customizations will be rebuilt from scratch in the fresh EspoCRM v10 instance, so I can avoid bringing over unnecessary legacy data or old system “garbage”.

[shalmaxb]

you can export the tables of your entities and import it in the new installation, overwriting the existing tables.