Cleaning a list does not mean deleting everything that looks old or retaining every address for hypothetical future campaigns. It means knowing where contacts came from, which communication is permitted, and what information is still necessary. For a business owner, a fresh import can look like a quick fix. Without checks, however, an import can restore unsubscribed people, create duplicates, and destroy the very context that made the database usable in the first place.
Keep the source, not just the address
For each contact category, identify the form, relationship, or process it came from. If you hold records of communication choices, keep them in a verifiable format. A column named consent, without context or provenance, may not explain the situation adequately. Purchased lists or files supplied by partners do not automatically become appropriate for your campaigns. Clarify permissions and responsibilities before use rather than waiting for a complaint to expose the uncertainty.
Treat duplicates as an identity problem
Two similar rows are not always the same person, and a shared address may represent a team. Define which details allow records to be matched and which cases require manual review. When merging, do not automatically overwrite an unsubscribe with an older value from another system. Keep relevant history and avoid decisions based only on names. An incorrect match can send one customer’s context to an entirely different contact.
Separate temporary errors from unusable addresses
Delivery failures do not all have the same cause. Platforms may distinguish temporary issues from addresses that cannot receive messages. Use the provider’s explanations and do not try to force repeated sends to contacts suppressed for serious reasons. If you move between tools, transfer relevant suppression records and rules. Otherwise, the new system may treat as available addresses that the previous system had already excluded for a valid reason.
Use a retention policy, not an impulsive rule
Commercial records, permission evidence, and information needed to honour an unsubscribe may serve different purposes. Decide what is retained, why, and who approves removal, taking applicable obligations into account. Do not keep unnecessary personal notes just because storage is available. At the same time, do not blindly remove the minimum suppression record if doing so would allow accidental reintroduction into a future campaign through another import or connected system.
Make the rule easy to hand over
Test the explanation with a concrete case: a new import contains an address already present in the unsubscribe suppression list. Can a colleague say what gets updated, who checks it, and which communication follows? If the answer depends on one person’s memory, document the rule somewhere the team can access. Include the meaning of important fields and situations requiring intervention, not just screenshots. Tool interfaces may change, but ownership needs to remain clear. Limit data access by role and keep personal details out of general documentation used for training or collaboration with suppliers. A useful handover describes the decision, not merely the buttons to press.
Check overlaps before launch
Use this test situation: a new import contains an address already present in the unsubscribe suppression list. Look at all communication that could reach the same person, not just the campaign currently being prepared. Check language, preferences, commercial relationship, and messages already scheduled. If two rules conflict, explicitly decide which takes priority and document why. Do not allow the accidental order of synchronisation jobs to determine the customer experience. Use test contacts and clearly labelled fictional data in an appropriate environment, without enrolling real customers in checks that could send messages or alter their commercial history. Test data is for verification, never evidence of business results.
Where deeper work is needed
These recommendations are a starting point, not a complete configuration. Advanced rules for priority, synchronisation, and exception handling depend on your data, tools, and team responsibilities. We leave those details out here: applying them without context can create new problems instead of resolving existing ones. Before expanding, assess the actual setup and validate the scenarios that matter to your business rather than copying a generic configuration into production.
Want to adapt these ideas to your business? Contact the the light team through the form on thelight.marketing, describing what you use today and where the process gets stuck.