Migrate from Knock CRM to Mailchimp

Knock's leasing pipeline has no native equivalent in Mailchimp

Knock models the leasing lifecycle as a visual pipeline with stages (Prospect, Touring, Applied, Lease Signed, Renewed). Mailchimp has no pipeline or deal-stage construct — prospects are flat subscriber records within an audience. We map each Knock pipeline stage to a Mailchimp group, but the visual Kanban-style pipeline in Knock does not translate. Teams lose the at-a-glance deal-flow view that Knock provides and must rely on Mailchimp's segment builder and group-based filtering to approximate it. Stage-transition timestamps are preserved as merge fields for reporting but Mailchimp's native reporting does not visualize leasing-stage progression.

Lease documents and property attachments cannot be stored in Mailchimp

Knock stores lease agreements, signed forms, ID copies, and tour photos as record attachments. Mailchimp's platform does not support file attachments on subscriber profiles. We export a manifest of all Knock attachment URLs mapped to each subscriber record and store the manifest reference as a custom merge field. Your team must move actual files to a separate storage system (Google Drive, Dropbox, or a property management document platform) and maintain the link manually. The attachment manifest preserves the connection between subscriber and document URLs for reconciliation, but Mailchimp will not host the files themselves.

Knock's task and follow-up system is completely excluded from migration

Knock's operational workflow — follow-up reminders, renewal task assignments, leasing-agent task queues, and day-overdue follow-ups — has no Mailchimp equivalent. Tasks in Knock are action items tied to prospects and properties that require human completion; Mailchimp automation flows are trigger-based email sequences. These are different mechanisms entirely. We export a task export CSV listing every open task in Knock with the associated prospect and due date. Your leasing team must rebuild follow-up logic as Mailchimp automation triggers using merge fields like LEASE_END and LEASING_STAGE. Any task logic that involves conditional routing based on Knock's environment system (e.g., team-specific assignment rules) cannot be auto-translated.

Mailchimp's subscriber model does not support property-unit hierarchy

Knock's data model links a prospect to a specific Property and Unit — the unit number, type, and lease terms are all related records. Mailchimp's subscriber model is flat: one contact record with merge fields. While we can store unit_number, unit_type, monthly_rent, and lease dates as merge fields on the subscriber, the property-unit relationship is denormalized into individual field values. If the same prospect inquired about multiple units across multiple properties in Knock, they collapse to a single Mailchimp subscriber record with multiple group memberships — the detailed unit-preference history is reduced to a tag list. Teams that rely on Knock's property-to-prospect relationship for reporting need to rebuild that logic in Mailchimp using group-based segments.

Bounced and unsubscribed status requires cross-system reconciliation

During the migration window (while both Knock and Mailchimp are active), subscribers who unsubscribe in Mailchimp need to be flagged in Knock to prevent re-engagement. Mailchimp maintains its own suppression list — contacts who unsubscribe in Mailchimp are added to Mailchimp's global_suppressed list and cannot be re-imported without a specific flag. Knock has no native Mailchimp suppression sync. We run a pre-migration suppression check against your Mailchimp audience and exclude bounced and unsubscribed addresses from the initial import. Post-migration, your team should enable Mailchimp's webhook-based suppression sync or use a third-party integration to keep unsubscribe status current between systems during the parallel window.