Contacts and lists
How to keep customer lists current: from CSV to ongoing updates
Repeated file uploads are not the only update method. First clarify each contact's identity, source and who controls updates to each field.
Maptinger · Content updated:
Step by step in the product
- Open CSV/Excel import in Contacts or add a record manually. Map columns to contact fields.
- Review invalid addresses, duplicates and identity conflicts; do not silently overwrite existing notes.
- Confirm the import and check list membership. A contact record or membership does not grant sending permission.
Separate contacts from lists
A person may be in both a prospects list and an event list. Use one contact with two memberships, not two contacts. Absence from a file does not mean deletion; establish whether the file is a full export or a batch of new records.
Preserve stable source identity
Reuse stable customer IDs from the source system. If an ID's email changes, review the change rather than merging automatically. A same-person decision must not bypass the previous opt-out through a new address. Imports should not silently overwrite manually corrected fields.
Track initial loads and changes separately
After an initial 10,000 contacts, 200 additions and 50 name changes should result in 10,200 unique contacts, not 10,250. This synthetic counting example is not a throughput guarantee. Separate custom-site API/form data from files, and distinguish source-reported completeness from provider verification.
Practical questions and answers
When should an Excel customer list move into a CRM?
A shared record becomes useful when several people edit the same contacts, follow-ups are missed or files disagree. Prepare stable customer IDs, field mapping and opt-out information, then preview a small file before migrating. In Maptinger, one contact can belong to several lists; a list membership is not a new customer identity.
Will my website's customer list synchronize automatically?
No. A custom-site connection needs a server-side setup implementing the existing API contract. Verify source ownership and the correct workspace, and monitor initial records, subsequent changes, errors and interruptions. A connection does not authorize changing another brand's opt-outs. We do not promise a setup-free connector for every site, including Shopify/ikas.
One contact, several lists: an update example
| Source ID | Incoming change | Expected handling |
|---|---|---|
| M-001 | Same contact, another list membership | Keep the contact; add membership |
| M-002 | Name field changed | Check field ownership and manual corrections |
| M-003 | Same ID, different email | Review identity; retain opt-outs if it is the same person |
Common mistakes
- Deleting contacts because they are missing from a file
- Treating imports as new marketing permission
How to approach this in Maptinger
Create a list in Contacts, map your CSV/Excel columns and inspect the import preview. Use stable source customer IDs where available. Start with a small sample to check additions, updates and review items.
Native Shopify/ikas customer synchronization has not passed release acceptance. The custom-site API does not make those connectors ready.
Related topics
How to plan sales automation: your first controlled workflow
Arrange triggers, conditions, tasks and human review in one workflow. Use one-off tools without building an automation first.
Read the guideWeb researchHow to research a company website with traceable sources
Inspect a supplied website or research web sources for a topic. Review findings and citations in the same research history.
Read the guide