Customer work, connected.

Help & supportMyAccount

CRM migration checklist

Move the relationships, not just the rows.

A customer export can look tidy while hiding important links between organisations, people, commercial records and conversations. A migration plan needs to preserve the meaning of those relationships as well as the field values.

Pixie CRM editorial team · Updated

Inventory the information you need

List the systems and files involved, the person responsible for each source and the records worth carrying forward. Separate active customer information from obsolete exports and material with no continuing purpose. Identify attachment types, historic notes, currencies, dates and custom fields early; these often require more preparation than a contact name.

Agree a field map and duplicate rules

For each source field, record its destination, format and whether a transformation is needed. Decide how to match organisations and contacts without treating a shared email address or similar business name as proof of identity. Preserve an appropriate source identifier so the migration team can reconcile records without exposing it unnecessarily to every user.

Test representative records safely

Use a controlled sample containing common records and known exceptions. Check linked contacts, ownership, dates, totals and permissions. Keep sensitive personal information out of casual email attachments and use an agreed secure transfer route. Confirm who is allowed to view the sample and when temporary migration files will be removed.

Reconcile before switching the team over

Agree record counts, spot checks and acceptance criteria before the final import. Plan how changes made during migration will be captured and who approves the transition. Confirm recovery and export arrangements with the service team, then retain only the migration evidence and source material your organisation actually needs.

Useful answers

What you might
be wondering.

Practical details for a better informed conversation.

Can we import every historic email?

That depends on the source, available export methods, agreed integration and the purpose of retaining the messages. Scope correspondence separately from basic contact data.

Who should clean the data?

The people who understand the customer relationships should approve matching and correction rules. Technical import work cannot reliably resolve every business ambiguity on its own.

Your workflow is a good place to start

Tell us what a better working day looks like.

Bring your current tools, your priorities and the handovers you want to improve. We’ll help you define a useful next step.

Discuss your requirementsAlready a customer? Open MyAccount

Verify your email. Send your enquiry.
Keep your ticket reference.

Find modules, practical guidance and support.

Press Esc to close.Browse every page