Contacts

Import in ten minutes. Stay legal for good.

Bring your list across from whatever you use now. Drop maps the columns, catches duplicates, records how each person consented, and refuses to email anyone who asked you to stop.

How it works

Three things it does well.

Your export, whatever shape it is in

Real exports have awkward column names, inconsistent capitalisation and duplicates. Drop expects that.

Columns detected for you
Email Address, Given Name, Surname. It works them out and lets you correct it.
Duplicates caught
Including the same address in different capitalisation.
Tells you what it skipped
Invalid addresses are reported with examples, not silently dropped.

Screenshot: column mapping, with columns detected automatically

Consent, recorded properly

GDPR asks you to show why you hold someone’s address, and when they agreed. Drop asks the why once, at import, and keeps each person’s own sign-up date and source from your export, so the record survives the person who imported them.

A basis on every contact
Signed up, bought something, met you at an event, or moved with you from another tool.
Their own sign-up date
Kept from your export when it has one, like Mailchimp’s opt-in time. Otherwise marked as the day they were added, never passed off as the day they agreed.
Export or delete on request
Both are one click, because both are rights.

Screenshot: the consent question at import

Unsubscribes that actually hold

In most tools an unsubscribe is a flag some code has to remember to check. In Drop the database refuses the write.

Enforced in the database
Not in application logic that could have a bug.
Survives re-import
Uploading an old CSV cannot resurrect someone who left.
Case-insensitive
The most common way people get wrongly re-added.

Diagram: an import attempting to re-add an unsubscribed address and being rejected

Send the next one.

The hardest email to send, and the hardest post to write, is the one after the last one you never did.