01AI and integrations · module
EspoCRM migration and parallel run
Compares and synchronizes records with EspoCRM during migration or parallel operation
- EspoCRM record mapping
- EspoCRM sync run
- Paired CRM records per configuration
- 10
- capabilities
- 3
- record types
- 3
- automations
- 2
- integrations and AI tools
02What the module does
Less routine. More value.
The EspoCRM integration pairs records in Draivix with records in an EspoCRM instance during migration or parallel operation. It highlights differences between both sides, imports changes, and can write updates back. Your business can transition from EspoCRM step by step and see exactly what differs before cutover.
- Know the differences before cutoverRecord comparison between Draivix and EspoCRM runs read-only and returns a discrepancy report. Before switching over, you know exactly how both sides differ.
- Matching by your own rulesThe key used to pair records is built according to your company settings, adapting the matching logic to how your data is structured in EspoCRM.
- You choose the sync directionSynchronization runs as import, write-back, or both. You can transition from EspoCRM gradually and control how data flows during the parallel run.
- Live runs require confirmationWithout explicit confirmation, synchronization executes as a dry run. Nothing is written to your data until you deliberately run it live.
- Read-only import from EspoCRMImport reads the EspoCRM database over a read-only connection, leaving your original system completely untouched while running alongside Draivix.
- Changes written back to EspoCRMWrite-back uses the EspoCRM REST API with an API key, ensuring changes made in Draivix also reach your original system during parallel operation.
- Clear status for every recordThe system classifies each record as unchanged, changed in source, changed in target, conflict, or missing record. You immediately see what needs attention.
- Conflicts never overwrite dataA record edited on both sides is flagged as a conflict and not overwritten. Your team’s work is never lost, even when data changes in both systems at once.
- Exact counts for every runEach run is logged with the exact number of processed, written, and conflicting records, giving you a clear, data-backed overview of migration progress.
- Parallel sync every 15 minutesOnce enabled by an administrator, scheduled synchronization runs every 15 minutes. Until it is enabled and the source profile and entity lists are configured, the job takes no action.
03How it works
How it works step by step.
What the integration does
When migrating from EspoCRM, both systems often run in parallel for a period of time. For every paired record, the integration maintains the link between Draivix and EspoCRM along with a content hash on both sides. That way, it knows which side has changed since the last synchronization.
Read in detail
Comparing both sides runs in read-only mode and returns a discrepancy report. The matching key is composed according to your company settings. This is especially useful before cutover when you need to see what differs.
Two-way synchronization
Synchronization runs as import, write-back, or both. Without explicit confirmation, it executes as a dry run. Import reads the EspoCRM database via a read-only connection. Write-back uses the EspoCRM REST API with an API key.
Read in detail
The system classifies every record into one category: unchanged, changed in source, changed in target, conflict, missing in source, or missing in target. Every run is logged with counts of read, written, unchanged, and conflicting records, plus records missing in the source. Rejections by EspoCRM (missing permissions, rejected record) are distinguished separately.
Conflicts and one-time changes
A record modified on both sides is counted as a conflict and is not overwritten. On the first synchronization, records paired by an earlier migration import take their values from EspoCRM once.
Read in detail
Write-back decides based on content hash comparison. Changing the field mapping therefore causes all paired records to differ once, so the next synchronization writes all of them.
Setup and operation
The scheduled job runs every 15 minutes, but does nothing until an administrator enables synchronization and configures the source profile and entity lists for import and write-back. Field mapping is part of the migration configuration prepared for your company. EspoCRM database access is stored in the server configuration, while the write-back API URL and key are in the company settings.
Read in detail
Imported records trigger standard system events. A companion command in the Automation module handles migrating workflows from EspoCRM.
04What runs automatically
Automations that save time.
Regular automatic synchronization
The EspoSync job runs every 15 minutes when synchronization is enabled and configured, so you do not have to maintain parallel operation manually.
Detects which side changed
During synchronization, the system compares content hashes and automatically categorizes records by which side changed. You see what happened without manual comparison.
Every run is logged
Each run is automatically logged with record counts and last-fetched markers, letting you trace what was transferred and where the next run will pick up.
External integrations
- Direct read from the EspoCRM databaseImport reads the EspoCRM database via a read-only connection and never writes to it. Database credentials are stored in the server configuration.
- Write-back with an API keyWrite-back runs through the EspoCRM REST API using an API key. You set the URL and key in the company settings, and the system distinguishes any rejections returned by EspoCRM.
05Frequently asked questions
Can I migrate from EspoCRM to Draivix gradually?
Yes. The integration matches records across both systems, pulls changes from EspoCRM and can write them back, so both systems can run in parallel.
What happens if a record changes in both systems?
It is counted as a conflict and is not overwritten. You can see the number of conflicts in the synchronization run log.
Can I review differences before switching over?
Yes. The comparison runs in read-only mode and returns a discrepancy report, and synchronization runs as a dry run unless explicitly confirmed.
How often is data synchronized?
Every 15 minutes, once an administrator enables synchronization and configures the source profile and entity lists.
- Companies, contacts and activitiesA single directory of companies and contacts, tasks, meetings, calls and AI meeting notes
- CRM and sales pipelineProspects, leads and sales opportunities with controlled stages, forecasting and cashflow
- Automation and workflowsNo-code “when X happens, do Y” rules and scheduled recurring records
- Data import and migrationControlled import from CSV, Excel or API with preview, error logging and rollback
- Migration from Raynet CRMTransfers companies, contacts, leads, deals, and activities from Raynet including full history
- AI assistant in DraivixAn in-app assistant that finds data, drafts changes and saves them once you confirm
Let’s start together
Tell us how your business works.
We will show you what a system that takes over part of that work could look like.
Book a consultation