CRM migration

Migrate from My Practice Now to Mailchimp

Field-level mapping, validation, and rollback between My Practice Now and Mailchimp. We move data and schema; workflows are rebuilt natively in Mailchimp.

My Practice Now logo

My Practice Now

Source

Mailchimp

Destination

Mailchimp logo

Compatibility

100%

12 of 12

objects map 1:1 between My Practice Now and Mailchimp.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

My Practice Now stores client records with contact details, appointment history, invoice data, custom properties, and staff assignments. Mailchimp structures its data around Audiences containing Contacts with standard merge fields (FNAME, LNAME, EMAIL, PHONE) and unlimited custom merge fields for extended properties. The migration extracts My Practice Now client records via the platform's API, maps standard fields directly to Mailchimp merge fields, and translates custom client properties into Mailchimp custom merge fields. Appointment data, invoice history, and service records surface as tags or custom field values so you can segment your audience by visit frequency, service type, or billing status. Automation workflows and email templates do not migrate — those must be rebuilt in Mailchimp's Customer Journey Builder using your migrated audience data. FlitStack AI sequences the migration so contacts load first, merge fields are created in Mailchimp before data arrives, and tags are applied in a second pass. A delta-pickup window captures any new clients or updated contact information during the cutover window.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

My Practice Now logo

My Practice Now

What's pushing teams away

  • Capterra reviewers cite poor customer service and unresponsive support as primary churn drivers, with issues remaining unresolved long enough to erode trust.
  • Negative reviews describe the software as non-intuitive and complicated, contradicting positive reviews and suggesting a steep or inconsistent onboarding experience.
  • Multiple reviews note that implementation is time-consuming and lengthy, which frustrates small practices with limited administrative capacity.

Choosing

Mailchimp logo

Mailchimp

What's pulling them in

  • Generous free tier with up to 500 contacts allows small teams to validate email marketing before committing to a paid plan.
  • Intuitive drag-and-drop email builder and 130+ templates let non-technical users produce professional campaigns without HTML or CSS knowledge.
  • 300+ native integrations, especially Canva and Shopify, make it easy to connect existing tools without custom development work.
  • Detailed open-rate, click-through, and campaign analytics give small businesses actionable insights without a dedicated marketing team.
  • One-platform consolidation of email campaigns, automations, landing pages, and ads reduces tool sprawl for lean marketing teams.

Object mapping

How My Practice Now objects map to Mailchimp

Each row shows how a My Practice Now object lands in Mailchimp, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

My Practice Now

Client

maps to

Mailchimp

Contact (Audience Member)

1:1
Fully supported

My Practice Now client records map directly to Mailchimp contacts on a one-to-one basis. The client email address serves as the primary contact identifier in Mailchimp's system. Clients without valid email addresses are excluded from the migration but are flagged individually in the migration report so your team can review and handle them manually after cutover.

My Practice Now

Client Custom Property

maps to

Mailchimp

Merge Field

1:1
Fully supported

Each custom property in My Practice Now (e.g., 'Preferred Therapist', 'Insurance Provider', 'Treatment Plan Status') becomes a corresponding Mailchimp merge field. Text properties map to TEXT merge fields; numeric properties map to NUMBER fields; date properties map to DATE merge fields. We determine field type based on My Practice Now's property type metadata.

My Practice Now

Appointment

maps to

Mailchimp

Tag + Merge Field

1:1
Fully supported

Appointment data does not have a direct Mailchimp equivalent in its contact model. We extract the most recent appointment date as a DATE merge field (LASTAPT) and apply service-type tags (e.g., 'Massage-Client', 'Initial-Consultation') to each contact. This approach enables you to segment your audience by visit recency and service category without native appointment objects in Mailchimp.

My Practice Now

Invoice

maps to

Mailchimp

Custom Merge Fields

1:1
Fully supported

Invoice status (Paid, Pending, Overdue) and outstanding balance amount migrate as custom merge fields on each contact record. Full invoice line-item history, tax breakdowns, and payment records are not supported in Mailchimp's flat contact data model. We preserve only summary financial fields (current balance and invoice status) to support billing-related segmentation in your campaigns.

My Practice Now

Client Note

maps to

Mailchimp

Tag / Note

1:1
Fully supported

Client notes in My Practice Now have no Mailchimp equivalent in the contact model. We flag notes containing important alerts (e.g., 'Do not email', 'Allergy alert') as tags on the contact record. Free-text notes are not migrated but can be exported as a separate CSV reference file for compliance or staff reference.

My Practice Now

Service / Package

maps to

Mailchimp

Tag

1:1
Fully supported

Service names and active packages assigned to a client map to Mailchimp tags on the contact. Multiple services result in multiple tags applied to the same contact. This enables RFM-style segmentation (recency, frequency, monetary value) based on the mix of services consumed by each client contact in your Mailchimp audience.

My Practice Now

Staff / Therapist

maps to

Mailchimp

Tag or Merge Field

1:1
Fully supported

The assigned staff member on each client record maps to either a tag (e.g., 'Assigned: Dr. Smith') or a dedicated STAFF merge field on the contact. This mapping supports rebooking campaigns where you want to target or exclude clients attributed to a specific provider. The choice between tag and merge field depends on your reporting needs.

My Practice Now

Client Group / Category

maps to

Mailchimp

Mailchimp Group

1:1
Fully supported

Client categories in My Practice Now (e.g., 'Active', 'Inactive', 'Prospect') map directly to Mailchimp Groups within your audience. Groups differ from Tags in important ways: Groups appear in Mailchimp's preference center where contacts can view and self-manage their category subscriptions, while Tags are internal segmentation labels invisible to contacts.

My Practice Now

Opt-out / Do Not Contact

maps to

Mailchimp

Contact Status (Unsubscribed)

1:1
Fully supported

Clients marked as 'Do Not Contact' or 'Email Unsubscribed' in My Practice Now are migrated to Mailchimp with unsubscribed contact status. This preserves suppression at the platform level, ensuring these contacts will not receive any email campaigns after cutover regardless of how they are included in your audience segments or groups.

My Practice Now

Client Created Date

maps to

Mailchimp

Merge Field (CLIENTDATE)

1:1
Fully supported

Mailchimp does not store contact record creation date as a native field. We preserve the original client creation timestamp from My Practice Now as a CLIENTDATE merge field on each contact. This enables you to run lifecycle reports, identify long-term clients, and segment your audience based on how long contacts have been in your system.

My Practice Now

Source / Referral

maps to

Mailchimp

Merge Field (REFERREDBY)

1:1
Fully supported

Referral source data captured in My Practice Now (e.g., 'Google', 'Friend Referral', 'Partner Clinic') migrates as a REFERREDBY merge field on each contact. This supports attribution reporting in Mailchimp campaign analytics, allowing you to track which acquisition channels drive the most engagement after migration and optimize your marketing spend accordingly.

My Practice Now

Client Phone

maps to

Mailchimp

Phone Merge Field

1:1
Fully supported

Client phone numbers map to Mailchimp's native PHONE merge field on each contact. SMS marketing in Mailchimp requires a separate SMS consent flag — we map the My Practice Now SMS opt-in property to an SMSOPTIN merge field. Both fields must be configured in Mailchimp before SMS campaigns can be sent to your migrated audience.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

My Practice Now logo

My Practice Now gotchas

Medium

Research data is sparse and often misattributed

High

Thinkific export scope determines what we can migrate

Medium

Content files require separate media migration

Mailchimp logo

Mailchimp gotchas

High

Contact count includes unsubscribed and non-subscribed records

High

Automation workflows cannot be exported

Medium

Account suspensions trigger silently during migration

Medium

Template HTML is Mailchimp-specific and may not render in other platforms

Medium

E-commerce data requires active store connection

Pair-specific challenges

  • Appointment history does not map to Mailchimp's activity log

    My Practice Now stores complete appointment objects with dates, services, staff, and notes. Mailchimp's contact model has no appointment equivalent — only email activity (opens, clicks, campaign sends) appears in the activity feed. We handle this by extracting the most recent appointment date as a LASTAPT merge field and applying service-type tags, but the full appointment history must live in a separate reporting system or be exported as a CSV reference file. If your re-engagement strategy depends on visit frequency segmentation, build that logic using the LASTAPT and service tags after migration.

  • Mailchimp charges by total contacts, not just subscribed ones

    My Practice Now may count all client records regardless of email status. Mailchimp's billing includes unsubscribed and archived contacts in the total contact count on paid plans. Before migration, we recommend reviewing the full client list and excluding clients with invalid emails or permanent unsubscribes — these can be suppressed separately in Mailchimp without incurring billing charges if handled through the suppression list rather than the main audience. This is a destination-side billing mechanism that catches teams unprepared for the contact-count math.

  • Merge fields must exist before contacts load

    Mailchimp requires merge fields to be defined at the audience level before data can populate them via import or API. My Practice Now's custom client properties need corresponding Mailchimp merge fields created manually or via Mailchimp's API before the migration run. We deliver a merge field creation checklist as part of the migration plan — if your audience already has contacts, adding merge fields retroactively does not backfill existing records. We can automate merge field creation via Mailchimp's API in the same migration run to avoid this gap.

  • Groups and Tags are separate segmentation systems

    Mailchimp distinguishes between Groups (opt-in categories shown in preference centers) and Tags (internal segmentation labels). My Practice Now's client categories can map to either, but the choice affects how clients appear in Mailchimp's UI and whether they appear in preference-center management. If you map client categories to Groups, clients can self-manage their subscription preferences. If you map them to Tags, they are invisible to contacts but fully usable for segmentation. We surface this decision point in the migration plan before data loads.

  • Invoice line items have no Mailchimp home

    My Practice Now invoice data includes line items, tax amounts, payment records, and balance due. Mailchimp's contact model supports only flat custom fields — it has no invoice object, no invoice-line relationship, and no accounts-receivable tracking. We migrate only summary invoice fields (current balance, last invoice status) as merge fields. Full invoice history should be exported as a standalone CSV from My Practice Now and archived separately. Mailchimp is not a billing or practice management tool and should not be treated as one after migration.

Migration approach

Six steps for a successful My Practice Now to Mailchimp data migration

  1. Pull My Practice Now client export and audit data quality

    FlitStack AI connects to My Practice Now via API using scoped read access. We extract all client records, custom properties, appointment summaries, and invoice balances in the first pass. We then run a data-quality audit flagging missing email addresses, duplicate contacts, invalid phone formats, and clients marked as 'Do Not Contact'. You receive a pre-migration data quality report so you can decide whether to clean records before the load or accept the flagged subset.

  2. Create Mailchimp merge fields and groups before data arrives

    Before any contact data loads, we create the merge fields in your Mailchimp audience that correspond to My Practice Now custom properties. This includes standard fields (FNAME, LNAME, EMAIL, PHONE, ADDRESS) and custom fields (CLIENTDATE, LASTAPT, NEXTAPT, BALANCE, STAFF, INVOICESTATUS, REFERREDBY, SMSOPTIN). We also set up the Groups that map to My Practice Now client categories. Merge fields are created via Mailchimp's API to avoid manual setup errors.

  3. Load contacts with direct field mapping and apply tags

    The migration loads contacts into your Mailchimp audience in batches. Direct field mappings (name, email, phone, address) populate merge fields in the first pass. In a second pass, we apply tags based on appointment service types, assigned staff, active packages, and flagged note alerts. Invoice summary data populates the BALANCE and INVOICESTATUS merge fields. Do-not-contact clients are loaded as unsubscribed to ensure suppression is honored.

  4. Run sample migration with field-level verification

    A representative slice of 100–500 contacts migrates first, covering a range of client types (active, inactive, with and without appointments, with custom properties populated). We generate a field-level diff between the My Practice Now source record and the Mailchimp contact so you can verify merge field values, tag accuracy, and group assignments before the full run commits. This is the reconciliation checkpoint before you cut over.

  5. Cut over with delta pickup for new or updated clients

    After sample verification, the full migration runs. During the cutover window (typically 24–48 hours), your team continues working in My Practice Now. A delta pickup captures any new clients, updated contact information, or new appointments that arrived during the migration run. Audit logging tracks every contact inserted, updated, or suppressed. One-click rollback is available if reconciliation reveals unexpected data gaps after go-live.

Platform deep dives

Context on both ends of the pair

My Practice Now logo

My Practice Now

Source

Strengths

  • Combines appointment scheduling, invoicing, and client notes in a single interface for small practices
  • Intuitive and simple to use according to positive G2 reviewers
  • Responsive development team that incorporates user feature requests
  • Mobile app allows creating and accessing client notes on the go
  • Great tech support cited by satisfied users

Weaknesses

  • Poor customer service and slow issue resolution reported in negative reviews
  • Non-intuitive and complicated interface according to some users
  • Lengthy, time-consuming implementation process
  • Inconsistent user experience — same product praised as intuitive and criticized as confusing
  • Sparse public documentation makes research and comparison difficult
Mailchimp logo

Mailchimp

Destination

Strengths

  • Free plan up to 500 contacts makes it the lowest-friction entry point for new email marketers.
  • Drag-and-drop builder and template library produce polished emails without design or coding skills.
  • Strong deliverability reputation backed by years of email infrastructure expertise.
  • 300+ native integrations cover the most common marketing stack combinations out of the box.
  • Consolidated platform for email, automation, landing pages, and ads reduces the number of tools small teams must manage.

Weaknesses

  • Contact-based pricing model charges for unsubscribed and non-subscribed records, inflating costs relative to competitors.
  • Five-step automation limit on Standard tier forces upgrades for basic customer journeys, a frequently cited frustration.
  • Template HTML is Mailchimp-specific and does not export cleanly for use in other email platforms.
  • Post-Intuit roadmap uncertainty means customers cannot confidently plan long-term platform investments.
  • Account suspension risk without clear pre-warning disrupts campaign scheduling for affected businesses.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across My Practice Now and Mailchimp.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    My Practice Now: Not publicly documented at the individual storefront level; Thinkific generally applies org-level rate limits.

  • Data volume sensitivity

    B

    My Practice Now doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your My Practice Now to Mailchimp migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about My Practice Now to Mailchimp data migrations

Answers to the questions buyers ask most during My Practice Now to Mailchimp migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your My Practice Now to Mailchimp migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most My Practice Now to Mailchimp migrations complete in 24–48 hours for under 10,000 client contacts. Larger datasets with 50,000+ contacts or setups with more than 20 custom client properties extend to 5–7 days. The longest step is creating Mailchimp merge fields before the load — we handle this via API in the migration plan so it does not add manual days. Pre-migration data quality review is the variable that most affects total timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from My Practice Now.
Land in Mailchimp, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day