Migrate from Demandforce to Mailchimp

Demandforce client records migrate directly to Mailchimp Subscribers. Each subscriber is assigned to an Audience (mapped from Demandforce Location or the practice account). Email address is the primary key for matching; phone numbers migrate as a Merge Field. We also preserve the original client creation timestamp as a Merge Field to support historical analysis and reactivation campaigns.

Demandforce Locations can map to separate Mailchimp Audiences (preferred for multi-location businesses) or be applied as a Tag (LOCATION_NAME) to all contacts from that location within a single Audience. We configure the strategy based on your Mailchimp plan and segmentation needs.

Appointment data (type, date, status) does not map to a native Mailchimp object. Instead, appointment type and last-appointment status migrate as Merge Fields (LAST_APPT_DATE, APPT_TYPE, APPT_STATUS) so Mailchimp Segments can filter contacts by recall window. Original appointment timestamps are preserved.

Demandforce recall program statuses (Recall Due, Recalled, Never Recalled) map to Mailchimp Tags (RECALL_DUE, RECALLED, INACTIVE). This enables Mailchimp Segments to isolate recall-due patients for targeted Customer Journey campaigns. We also retain the recall interval configuration as a custom Merge Field to help you set precise timing for follow-up outreach based on practice-specific schedules.

Demandforce custom client properties (preferred provider, treatment history, insurance type) map to Mailchimp Merge Fields. Field types (text, date, number, pick-list) are converted to matching Mailchimp field types. Pick-list values are preserved as Merge Field options or applied as Tags.

Demandforce email campaigns do not migrate — Mailchimp campaigns have a completely different architecture (template builder, subject line, audience selection, send settings). We export Demandforce campaign names and send dates as a reference for rebuilding in Mailchimp's campaign builder. Your team can use this export to replicate campaign logic, recreate templates, and schedule sends that align with previous outreach patterns.

Review request status (Requested, Submitted, Published) migrates as Mailchimp Tags (REVIEW_REQUESTED, REVIEW_SUBMITTED, REVIEW_PUBLISHED). This lets you segment patients who have and haven't left reviews for follow-up outreach. We also map the date of each review request to a Merge Field, enabling you to target contacts whose request is overdue or whose review is pending after a set period.

Two-way text message history in Demandforce has no Mailchimp equivalent — Mailchimp does not include SMS functionality in its core platform. If SMS is critical, you would need a companion SMS tool (e.g., Klaviyo SMS or a dedicated texting platform) and rebuild message logs separately.

Demandforce automated appointment reminders and recall sequences do not migrate. They must be rebuilt in Mailchimp's Customer Journey builder using the appointment-status Merge Fields and recall Tags we migrate. We provide a Demandforce workflow export as a rebuild reference. After migration, you can use the exported workflow details to configure triggers, set delays, and design email paths that reflect your original recall cadence and reminder schedules.

Demandforce's thank-you email triggers (sent when appointment time card is billed) have no direct Mailchimp equivalent. Rebuilding requires Mailchimp automations triggered by appointment status changes fed from your practice management system. We recommend setting up a Customer Journey that applies a tag when an appointment is marked complete, then sends a personalized thank-you email based on the service type.

Demandforce reputation management and business listing data (review monitoring, listing management) does not migrate — these are platform-specific constructs. Your review monitoring would need to continue in a dedicated reputation tool or be re-established independently. If you rely on Demandforce for local SEO tracking, you may consider tools like Moz Local or Yext to preserve your listings and monitor ratings across multiple directories.

Demandforce links clients to staff members (e.g., assigned provider). These map to Mailchimp Tags (STAFF_ASSIGNED or similar) on the subscriber record, allowing segmentation by assigned staff for internal routing or personalized email sends. We also store the staff identifier as a Merge Field, enabling you to include the provider's name or contact details in personalized email content and track performance by staff member.