Review likely duplicates before uploading a Customer CSV. Daylane checks repeated identities within the file and applies separate matching rules when adding records to your business. Those checks serve different purposes. A successful preview does not mean that every row will create a new Customer.
Compare identities, not just spelling
Keep a copy of the original file and review a working copy. Group likely matches by email and then phone, checking names and the actual customer relationship before combining anything. Two properties can belong to one customer, while two unrelated customers can share an office inbox.
| Rows being compared | What to check | Action after confirmation |
|---|---|---|
| Example Co / EXAMPLE CO with the same email and phone | Same customer entered twice? | Keep one current row |
| Example Co / Example Company with the same email | Different names for the same relationship? | Resolve manually; both may pass the file duplicate check |
| Two customers using accounts@example.com | Shared inbox for distinct customers? | Do not assume import will preserve both; review individually |
| One name with different phone spacing | Same number stored differently? | Choose a consistent verified representation |
Understand the file-level check
Within a file, Daylane identifies a duplicate using the name in lowercase, email in lowercase and trimmed phone together. It trims surrounding spaces but does not standardise phone formatting. A different name or differently spaced phone can therefore avoid that exact duplicate check even when the rows refer to the same person.
Fix reported row errors before importing. Do not change a correct customer name simply to get past a duplicate warning; decide which record you intended to bring across.
Understand what happens when importing
If an incoming row has an email matching an existing Customer in the business, Daylane skips that row. If the incoming email is blank, an exact existing phone match also causes a skip. This also applies to records added earlier in the same batch. A skipped row does not update notes or add its Location.
An incoming row with an email uses the email match, not a fallback phone match. Rows without either email or phone have no existing-record match on those fields. Re-uploading such rows can create extra Customers, so reconcile the first result before retrying.
Keep a separate list of resolved exceptions
Record which source rows you kept, which you removed and which existing records need manual review. That small reconciliation list is more useful than repeatedly uploading slightly different files. Check the imported and skipped counts against it after the import completes.
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.