After importing Customers, compare the imported and skipped totals with your intended list, then inspect representative records and every known exception. A completed import confirms that records were processed. It does not confirm that the source file had the right customer, destination or contact information.
Reconcile the counts first
Keep the exact file used and note the result before preparing another upload. In this fictional example, a ready preview contains 80 Customers. The result reports 73 imported and 7 skipped. The result accounts for all 80 rows, but the seven skips still need explanation.
| Measure | Count | Next check |
|---|---|---|
| Rows in ready preview | 80 | Matches the cleaned source list |
| Imported Customers | 73 | Inspect new contact details and expected Locations |
| Skipped Customers | 7 | Match to existing records or earlier matching rows |
| Unaccounted rows | 0 | 80 minus 73 minus 7 |
Check records with different shapes
Inspect a Customer with no Location, one with a complete Location, one with a leading-zero postcode and one with punctuation or a non-ASCII character in its name. Include every record you corrected during preparation. Sampling is a useful first pass; it cannot prove that every row is correct.
- Compare name, email and phone with the cleaned source.
- Check the full service address, including the four-digit postcode.
- Confirm Customer internal notes went into the intended field.
- Review each known duplicate, shared inbox and missing-contact exception.
Do not treat a skip as an update
Daylane skips a matching existing email, or an exact phone match when the incoming email is blank. That row does not replace the existing Customer's details or add the incoming Location. Open the existing record to resolve any change you intended to make.
If two different source customers share one email, investigate the relationship before deciding how to represent them. Re-uploading the same file cannot resolve that ambiguity, and rows without email or phone may be added again.
Verify the first real booking
When creating the next genuine Job, select the imported Customer and confirm the intended Location. Add any additional Locations through the Customer record. Check the contact used for scheduling messages and the instructions needed for attendance before confirming the Visit.
Retain a short exception list with an owner and next action for anything unresolved. Do not mark the migration ready merely because the first ten preview rows looked correct; the preview is limited and the final scheduling check serves a different purpose.
Sources and scope
An original operational guide from the Daylane team at Blu Mint Digital. Scenarios, durations and message wording are illustrative planning examples, not customer results or industry benchmarks. Product references were checked against the Daylane implementation on 5 September 2026. Adapt the workflow to your service, customer agreements and working conditions.
How we write and maintain our guides. Free templates and planning tools.