Moving to a new CRM is a chance to start clean, and a risk of losing history the sales team relies on. Most problems come from moving everything without checking it, or from moving too little and finding out later. This checklist covers what to move, how to prepare it and what to leave behind.
Before you export anything
- Set a cut-over date. From that day, new enquiries go into the new system only.
- Name one owner for the migration, with time set aside to do it.
- Set up the new system first: pipeline stages, event types, lead sources, lost reasons, tags and users. The import maps onto these lists, so they need to exist.
- List every place data lives today: the old CRM, spreadsheets, the shared mailbox, wedding portal accounts, a paper or Excel diary and the PMS.
What to move, and what to leave
| Data | Move? | Notes |
|---|---|---|
| Contacts with a current relationship | Yes | Name, email, phone, company, job title, and marketing consent with its source. |
| Companies | Yes | Name, website, address, VAT or registration number. |
| Open enquiries | Yes, with care | Event date, guests, value, stage, owner and next action. |
| Future confirmed events and holds | Yes | Check each one against the diary and the PMS. |
| Won and lost history | A defined period | Enough for repeat business and year-on-year comparison. Agree the period first. |
| Email history | Usually not by import | Keep the old system or an export as an archive. |
| Signed contracts and documents | Archive | Keep them where they can be found, with a reference on the record. |
| Unsubscribes | Yes, always | Losing them means emailing people who opted out. |
| Test records, spam, bounced addresses | Leave behind | They add noise and nothing else. |
| Old contacts with no consent and no recent business | Usually leave behind | Apply your data retention policy before you move, not after. |
Clean the data before you move it
- Remove duplicate contacts, using the email address as the main match.
- Split full names into first name and surname where the new system needs it.
- Standardise company names and add the website domain where you have it.
- Fix names typed in capitals and obvious typing errors in email addresses.
- Map old stages and sources to the new lists in a simple two-column sheet.
- Delete test records and spam.
- Tag the import batch, for example "Imported 2026", so you can find these records later.
Consent and data protection
Moving data does not renew consent. Carry marketing consent across as its own field, with the source and date where you have them. Do not mark contacts as consenting because they were in the old system. Carry unsubscribes across, and check your plan with whoever looks after data protection at the hotel.
Open enquiries need the most care
An open enquiry is a live conversation. For each one, the new system needs the owner, the stage, the next action and any held space, plus the latest proposal. For a small pipeline, re-entering open enquiries by hand is often quicker than building an import, and it doubles as a pipeline review: anything nobody wants to retype is probably lost already.
Check every future hold and confirmed event against the diary and the PMS on the cut-over day. A missing hold is how double bookings happen.
Test with a sample first
- Import 20 to 50 rows.
- Open several records and compare them field by field with the source.
- Check the totals: rows in the file, records created, records matched to existing ones, rows skipped.
- Fix the mapping, then import the rest.
Run the old system read-only
Keep the old system available for look-ups for a set period, but stop entering data in it on the cut-over date. Two live systems mean two versions of every client.
The first four weeks after go-live
The work does not end on the cut-over day. Plan a short review each week for the first month:
- Week 1: check that every new enquiry source, such as the website form, wedding portals and the shared mailbox, lands in the new system.
- Week 2: look for duplicates created by the import and merge them.
- Week 3: compare the pipeline value with the figure from the old system on the cut-over day, and explain any large difference.
- Week 4: ask coordinators what they still look up in the old system, and decide whether that data needs to move after all.
Migration checklist
- Cut-over date and owner agreed.
- Stages, sources, event types, lost reasons and tags set up in the new system.
- Data sources listed.
- Contacts and companies cleaned and de-duplicated.
- Consent and unsubscribes carried across.
- Open enquiries, holds and future events checked one by one.
- Sample import tested.
- Old system set to read-only.
How Staybase handles this
Staybase Sales & Events imports contacts and companies from a CSV or Excel (.xlsx) file of up to 20 MB and 20,000 rows. Import settings apply a source label, a tag, a note and an optional follow-up task to every contact, and decide whether new records are visible to the whole group or one hotel. Columns are mapped to fields, including Full name (will be split) and Marketing consent (GDPR). A check step shows what will happen to every row before anything is saved.
Existing contacts with the same email are not duplicated; they receive the tag and the note instead. Companies are matched by domain or name, and new companies can be filled in from their website. The import creates contacts and companies, not leads, so open enquiries are added on the pipeline. Find duplicates groups contacts with the same name or phone for merging.
When a coordinator connects a mailbox, the first check goes back 7 days, and adding a contact by hand pulls in recent emails from Microsoft 365. Events already in Guestline Rezlynx can be imported from the From your PMS card without changing the booking. A Data retention setting anonymises contacts without consent or open enquiries after a set number of months.
To plan a move to Staybase with your own data, book a demo at staybase.co.uk.