Migrate from Perfect Books to Mailchimp

Each Perfect Books Contact becomes a Mailchimp subscriber within the target audience. Email address is the unique key — subscribers without an email address are flagged for review before migration, since Mailchimp requires a valid email for every contact record.

Mailchimp has no native company object — the company name from Perfect Books maps to a custom or standard merge field labeled COMPANY. When contacts share a company name, Mailchimp will show duplicates by company value; consider pre-consolidating company names in Perfect Books before migration.

Perfect Books deal stages and pipeline names are translated into Mailchimp subscriber tags on each contact record. We create one tag per pipeline stage or deal label so you can build Mailchimp segments filtering by tag to reproduce deal-based audience logic and track pipeline progression across your migrated contacts.

Mailchimp caps merge fields at 255 characters. Long-text Perfect Books custom properties are truncated at 255 characters during migration and a warning flag is logged for each affected record so you can decide whether to split the data into two merge fields or store it in an external reference.

Perfect Books subscription status values map directly to Mailchimp member statuses using a 1:1 translation: 'subscribed' maps to 'subscribed', 'unsubscribed' maps to 'unsubscribed', and 'bounced' maps to 'unsubscribed' with the specific bounce type preserved in a separate custom merge field for reference and potential re-permissioning workflows.

Mailchimp does not include a native owner field on subscriber records. We preserve the Perfect Books owner email as a custom merge field (OWNER_EMAIL__c) so your sales and marketing teams can trace which rep was associated with each contact before the CRM transition and continue routing based on assignment.

Mailchimp tracks opens, clicks, and unsubscribes natively for campaigns sent from within Mailchimp, but there is no native equivalent to CRM call logs, meeting records, or emails logged before the migration. We surface engagement history from Perfect Books as a JSON-encoded custom merge field for reference only.

Perfect Books notes attached to a contact migrate as Mailchimp Notes on the subscriber record, preserving the original author name and creation timestamp in the note body so the full context remains readable within Mailchimp's contact timeline view for your team.

Perfect Books static and dynamic lists merge into a single Mailchimp audience. Each source list name becomes a tag applied to all subscribers originally included in that list, preserving the original list-membership signal without requiring separate audiences for every source list.

Mailchimp does not store files natively on subscriber records. File attachments from Perfect Books are exported to cloud storage and the URL is stored in a custom merge field. Your team configures the storage bucket and access policy before migration runs.

Perfect Books workflows, sequences, and automation rules have no direct Mailchimp equivalent and must be rebuilt manually. FlitStack AI exports workflow definitions as a structured JSON document along with a reference guide so your Mailchimp admin can reconstruct the original logic in Mailchimp Customer Journeys.