Mailchimp → Cyberimpact
Cyberimpact imported eight consented test contacts. A later opt-out stayed excluded through two reimports. No mailing was sent.
Reviewed
Acceptance checks
1. Eligibility and exclusions
PassedThe live export accounted for 15 in-scope contacts. Eight with consent were imported. Four unsubscribed and three non-subscribed contacts were excluded. A separate 20-row rehearsal yielded eight eligible and twelve excluded. It covered cleaned addresses, missing proof and conflicting status. Every row was accounted for.
Acceptance criterion
Every source record reconciles to eligible-imported, deliberately excluded or rejected. Zero unexplained records.
2. Suppression in a sendable selection
PassedOne test contact opted out in Cyberimpact and remained unsubscribed after two historical reimports. The unsent mailing selected exactly the other seven consented contacts. No suppressed or consent-unknown contact was selected.
Acceptance criterion
Zero suppressed or consent-unknown examples appear in a sendable selection; if native suppression cannot be demonstrated, the live-send gate remains blocked.
3. Field quality and consent history
PassedAll 56 agreed field values matched for eight contacts. There were 48 literal matches and eight equivalent language labels. Accents and leading zeros survived. The free plan used Memo for the pilot code. The consent ledger retained the original UTC instant while Cyberimpact stored the date.
Acceptance criterion
100% of mapped names, language preferences and supported custom fields match; retained source consent evidence and timestamps remain accessible.
4. Repeat imports and deduplication
PassedTwo repeat batches from the subscribed export and consent ledger reproduced all 56 baseline values. Cyberimpact added zero contacts. The English batch had four existing contacts. The French batch had three existing contacts and one suppressed historical record. The final groups contained four English and three French contacts.
Acceptance criterion
Group membership and deduplication behave as documented for the pilot. Reimport does not silently broaden permission or create unintended recipients.
5. Destination readback
PassedNative contact and consent screens reconstructed all seven agreed fields for each of eight contacts. A separate baseline CSV was generated, but browser delivery was blocked, leaving its portability unverified. Domain and sending configuration stayed in place. No email was scheduled or sent.
Acceptance criterion
A destination readback or export can reconstruct the agreed contact fields. No domain, DNS or live sending configuration changed.