Skip to content
English

Data Migration

Your data, moved into a new or renewed system: complete, correct and ready to work on from day one.

Changing a system is a decision about software. Whether it works is a decision about data.

The new system is chosen and the licences are bought. Then someone asks what happens to years of customer history, open deals and tickets, invoices, and every email conversation attached to them. The project either has an answer at that point, or it stalls.

We are that answer. Data migration is our core work: we move a business's existing data into a new or renewed system, rework it to fit, set the system up to receive it, and stay until your team works on it.

At a glance

  • Any system: CRMs, ERP and accounting systems, databases and files
  • Any direction: into a system, out of it, or between two of the same kind
  • Full history: records, links between them and email conversations
  • No stoppage: a plan you approve first, and a cutover around your calendar

What is data migration?

Data migration is moving your existing data into a new or renewed system and bringing that system into use. The data is reworked to fit, and the system is set up to receive it. The project ends when your business works on the system in its new form.

It happens in more situations than a straight replacement:

  • Replacement: a new system takes over from an old one.
  • Consolidation: two or more systems are merged into one.
  • Fresh start: a system already in use is set up properly after a trial, an upgrade or a period of neglect.
  • New data: a system receives data that used to live in other systems, spreadsheets or files.

Migration is one-time. Keeping two systems that both stay in use continuously in step is systems integration.

What do we migrate?

Every migration follows the same method. What changes is the kind of system your data moves into.

CRM Migration

Into a new or renewed CRM, from another CRM, an ERP, spreadsheets or databases: HubSpot, Pipedrive, Salesforce, Freshsales, SugarCRM, Brevo and others. Including merging several CRMs into one, leaving HubSpot, or starting over in the CRM you already have.

ERP Migration

Into a new or renewed ERP or accounting system, from another ERP, a CRM or spreadsheets: customers, products, price lists, invoices and payments, with their financial meaning kept.

Other systems

Into any other kind of system, discussed case by case: a database moving to a new platform, files moving into a specialised system for your sector, or data from MS Access, SQL databases, Notion, SharePoint or Google Drive.

Why do most migrations disappoint?

They technically succeed. Everything arrives. And then nobody trusts the new system, for reasons that have nothing to do with moving data from one place to another:

  • The history didn't come. Records made it; conversations, notes and context did not. Your team has a clean database with no memory, and keeps the old system open in another tab.
  • The duplicates came too. Nobody dealt with them on the way, so the new system launches with the same mess as the old one, except now it looks official.
  • The data arrived, but wrong. Fields were mapped to destinations that look right but mean something different. Nobody notices until a report doesn't add up, months later.
  • The business stopped. A week of frozen work while the transfer runs is not a technical necessity. It is a planning failure.

How do we do it differently?

We plan before we move, and you sign it off

Every migration starts with a data mapping table and a migration plan: what goes where, what is transformed, what is left behind and why. You approve it in writing before a single record moves.

We assess your data first

Before any record moves, we assess the source data and report every issue: duplicates, inconsistent formats, fragmented records and missing values, each measured and sized, so you know what it costs to fix and what it costs to ignore.

We keep your history

Email conversations, notes, meetings, tickets, invoices and the links between records. It is the hardest part of a migration and the first thing many providers leave out. Your team should open the new system and recognise it.

You verify it yourself

We build views inside the new system so your own people can check their own data, rather than read a report that says everything is fine.

Your business keeps running

New entries in the old system are frozen only for a few days before cutover, and it stays available read-only while the new one comes up. Your team keeps working throughout.

How does a migration project run?

Six phases, each with a checkpoint:

  1. Extract: full record sets are pulled from the source, after a complete backup of it is kept.
  2. Analyse: the data quality assessment is carried out, and transformation rules are defined against the destination's data model.
  3. Clean (optional): the issues found are corrected, if you choose to have it done.
  4. Transform and match: fields are mapped, records are matched across sources, and custom fields and objects are created where no equivalent exists.
  5. Import: data is loaded with the destination's import tools and its API, chosen object by object around the platform's real limits.
  6. Test: integrity checks against the source, testing with your daily users, and a full reconciliation report.

A full CRM replacement usually takes four to eight weeks, depending on the volume of data, the number of objects, the quality of the source data and whether cleaning is included.

What does every project include?

  • A data quality assessment before the move, with every issue sized and reported
  • A data mapping table and migration plan, agreed in writing
  • Transformation to the destination's structure, including custom objects and fields
  • Matching of records across sources, when several systems are merged
  • Setup of the destination for the data actually arriving
  • Import, user acceptance testing and a reconciliation report
  • Verification views and validation rules in the destination, so the data stays clean after go-live
  • A correction period after handover

Optional, quoted separately: data cleaning and deduplication, and pseudonymisation of sensitive data. Which duplicate wins and which format becomes the standard stays your decision. If you skip cleaning, your data moves as it is, with every issue documented. The validation rules in the destination follow our rules enforcement work.

Why work with us?

We are independent

We are not tied to any platform, so we move data in any direction, including out of HubSpot, with the same care. Our advice follows your interest, not a vendor's.

Experience across systems

We have migrated data between CRMs, ERP and accounting systems, spreadsheets and legacy databases. We know where each kind of migration goes wrong, and we plan around it from day one.

We understand what your data means

We have worked with businesses of every size. That tells us what a field really means in your sales process, your invoicing or your customer service, so the data arrives working the way your business does.

Case studies

Migrations we have delivered, and what made each one work.

Merging two CRMs into HubSpot, without losing a single email

Pipedrive and Freshsales consolidated into HubSpot, with full email history.

Replacing SugarCRM with HubSpot, with zero downtime

Years of heavily customised data moved in six weeks, without stopping work.

From unstructured files to a working CRM

A structured HubSpot built from scattered files in 35 working days, including a custom object for a vessel fleet.

Planning a migration? Book a free consultation and we will look at your systems, your data and the safest way to move it.

Frequently asked questions

How long does a data migration take?

A full CRM replacement usually takes four to eight weeks. Simpler moves take less. The time depends on the volume of data, the number of objects, the quality of the source data and whether cleaning is included. We give you a timeline once we have seen your data.

Will our business have to stop during the migration?

No. New entries in the old system are frozen only for a few days before cutover, and the old system stays available read-only while the new one comes up, so your team keeps working throughout.

What is the difference between data migration and systems integration?

A migration moves your data once, into a new or renewed system, and then ends. An integration is a standing connection between systems that both stay in use, so data entered in one is correct in the other.

Can you move our email conversations and history?

Yes. Email conversations, notes, meetings, tickets and the links between records are moved and attached to the right records. Keeping history is one of the main things we plan for.

Do you clean our data as part of the migration?

Every migration includes a data quality assessment, so you know exactly what is wrong with your data. Cleaning and deduplication are optional and quoted separately once you have seen the assessment. If you skip them, the data moves as it is, with every issue documented.

Can you migrate data out of HubSpot?

Yes. We migrate in any direction, including out of HubSpot and between two systems of the same kind.

Can several systems be merged into one?

Yes. Records that exist in more than one source are matched into a single record, and conflicting values are resolved with you before the move.

Our data is only in spreadsheets and files. Can it still be migrated?

Yes. When there is no existing structure to map from, we design the destination's structure first, then load the data into it.

Which systems do you work with?

Mostly CRMs such as HubSpot, Pipedrive, Salesforce, Freshsales, SugarCRM and Brevo, ERP and accounting systems such as Elorus, SQL databases, MS Access, Excel and Google Sheets. Other systems are discussed case by case.

How do we start?

Book a free consultation. We look at your current systems, your data and where it needs to go, and tell you how we would approach the move.

Latest posts

You can spend a few minutes checking out our latest articles, covering various subjects around data.