Before moving your team to an online CRM, find out whether a colleague can take over an enquiry without calling the person who last handled it. Can they find the quote the customer received, see what was promised and tell when to follow up? Use ordinary sales work for the trial, including a case that does not follow the usual sequence. Decide in advance what would stop the rollout. A missing follow-up date on an open quote, for example, is a more urgent problem than a report that needs reformatting.
1. Test the work, not the feature list
Take an enquiry that represents a typical sale. A customer asks for a quote, clarifies what they need on a call and then goes quiet. In the trial, have one person log the enquiry and another take it through to a follow-up. Ask the second person to identify the customer’s latest request, find the version of the quote that was actually sent and work out when to make contact again. If they have to search a private inbox or ask the original owner what was agreed on the call, note exactly what was missing from the shared record.
Give each sales stage a name that tells the team what has happened. “Quote sent” records an event; “in progress” could mean almost anything. Agree where to record the next action, who is responsible for it and when it is due. Include a messy case in the trial: perhaps the buyer replies to an old thread after the opportunity was closed. Can a colleague tell whether to reopen it or start a new opportunity without losing the earlier conversation? If you are deciding what belongs in the CRM in the first place, review the sales CRM overview with those tasks in mind. Keep a distinction between following up on a quote and maintaining the accounting records for a sale.
2. Check what comes in and what can go back out
Run a sample import before moving the full dataset. Choose records likely to expose problems: two people at one company, several opportunities for one customer, a note with multiple lines and a phone number with an international prefix. Map the old columns to the new fields and use fictional records where they are enough to test the format. You do not have to migrate every historical record. If you keep older documents in an archive, tell the team where to find them and check that the people who need them have access.
After the import, open individual records. A matching row count will not tell you that two contacts were merged incorrectly or that a quote is now attached to the wrong opportunity. Confirm that owners and dates carried over and that open work is still distinguishable from completed work. Treat contacts that share a company email address as possible duplicates, not automatic matches. Import a revised sample as well. You want to know whether a second attempt updates existing records or creates another set before you have to correct the live import.
Export the test data and open it outside the CRM. Can you link an opportunity to the right contact using the exported files alone? Check whether notes, attachments and activity history are included in the main export, available separately or missing. A readable export is useful, but it does not prove that you can restore the workspace after a mistaken bulk edit. Ask who can request recovery, which records or settings can be restored and what happens to changes made after the point you would restore to.
3. Try permissions, outages and integrations in practice
Test with the accounts people will actually use. An administrator seeing a record tells you little about what a sales colleague can see. Ask a colleague to cover an enquiry using their normal permissions. Check that they can find the notes and take ownership of the follow-up. Check also that they cannot do things their role does not require, such as export the whole contact list or change the sales stages for everyone. Decide who removes access when someone leaves and who takes over their open work.
Try the basic tasks on the devices your team uses away from a desk. If colleagues log calls on their phones, have them find a contact and record the next action on a phone rather than watching someone do it on a laptop. Agree where to capture essential details temporarily if the service or your connection is down. Assign someone to compare those notes with the CRM once service returns, so work is neither lost nor logged twice. Use a disposable record to see what happens to a half-written note when the connection drops.
Treat any connection to email, calendars or website forms as unproven until you have tested it. Send a fresh message, reply in an existing thread and forward a message from another mailbox. Check which record each message lands on, who can read it and how you would notice if it was not linked at all. If you are considering automation, use the AI workflow overview to help scope a narrow trial. An internal reminder is easier to check than a series of messages to customers. Verify that the reminder stops when the opportunity closes. If you test a drafted reply, have someone check prices, dates and other commitments before it goes out.
4. A pilot for a four-person installation business
Imagine a business that installs blinds for small offices. An office coordinator takes enquiries by phone and email, two colleagues visit sites and prepare quotes, and the owner reviews work waiting for a decision. The shared spreadsheet shows that a quote was sent but not whether the customer is waiting for a fabric sample or the team is waiting for measurements. When a colleague is on a site visit, the coordinator cannot always answer a customer who calls for an update.
On Monday, the team imports a small set of open jobs and compares the records with the spreadsheet and quote files. One property manager is listed against two sites. Rather than create a duplicate contact to distinguish the jobs, the team checks whether the CRM can keep them separate while linking both to the same person. For the rest of the week, the coordinator logs new enquiries in the CRM and uses the spreadsheet to look up older records. People update pilot enquiries only in the CRM so there are not two competing versions. At the end of each day, the coordinator checks the new entries against the inbox and call notes.
On Wednesday, the owner asks one colleague to cover a quote prepared by the other. The covering colleague finds the sent quote but cannot tell who was meant to confirm the fitting date. The team changes its handover rule: every open quote must say who is expected to act and when the team will check again if nothing happens. On Friday, they repeat the handover with a different quote. They will move the remaining open work only if they can match it against the old list and a colleague can handle a customer callback without chasing the original owner for context.
5. Use a go-live checklist
- Trace an enquiry from each source to an assigned owner and a clear next action.
- Have a colleague take over an opportunity using only the shared record and their normal permissions.
- Check the imported sample for wrong links, missing notes, changed dates and duplicates.
- Open the export files, note what they omit and confirm separately what can be restored.
- Rehearse an access change and agree how to log work during an outage.
- Test each integration with a normal case and one that arrives twice or does not link as expected.
- Choose the switch time, appoint someone to reconcile open work and tell the team where to log new enquiries.
Before approving the move, compare the pricing plans with what you actually tested. Account for the time needed to clean data, train the team and maintain the setup, not just the subscription cost. At the agreed switch time, capture any last changes in the old system and reconcile the open opportunities before making it read-only. If that check reveals a gap that could cause a missed customer commitment, postpone the switch and tell everyone where to log new enquiries and update existing ones until you can run the check again.
