CRM migration

Migrate from My Practice Now to Pipedrive

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

My Practice Now logo

My Practice Now

Source

Pipedrive

Destination

Pipedrive logo

Compatibility

87%

13 of 15

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

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

My Practice Now stores client records, appointment history, invoicing, and custom intake fields in a practice-management model designed for healthcare and wellness providers. Pipedrive's CRM model uses People (contacts), Organizations (companies), Deals (opportunities), Activities (tasks/events), and custom fields scoped per object. These architectures diverge significantly: appointments become Pipedrive Activities with type and duration stored as custom fields, invoices have no native Pipedrive equivalent and require a custom Invoice object, and practitioner-owner resolution maps by email match to Pipedrive users. FlitStack AI extracts My Practice Now data via API export, maps each object to its Pipedrive counterpart using type-aware field transformation, creates any required custom fields in Pipedrive before import, and sequences the migration so foreign keys resolve correctly. Workflows and automations in My Practice Now do not migrate — they must be rebuilt in Pipedrive's automation engine. The delta-pickup window captures any records modified during cutover, and one-click rollback is available if reconciliation fails.

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

Pipedrive logo

Pipedrive

What's pulling them in

  • Clean drag-and-drop pipeline interface with minimal learning curve, making it approachable for small sales teams without dedicated CRM admins.
  • Visual deal tracking keeps reps focused on next actions — activities, calls, and follow-up tasks surface directly in the pipeline view.
  • Strong integrations via Zapier and native marketplace apps let teams wire Pipedrive into Calendly, ActiveCampaign, and similar sales-stack tools.
  • Mobile apps for iOS and Android keep field reps connected to deals, contacts, and tasks without a desktop session.
  • Reputation and review volume — over 3,000 verified reviews across G2 and Capterra — signal reliability for teams evaluating CRM options.

Object mapping

How My Practice Now objects map to Pipedrive

Each row shows how a My Practice Now object lands in Pipedrive, 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

Pipedrive

Person

1:1
Fully supported

My Practice Now client records map directly to Pipedrive People. Fields like first name, last name, email, phone, address, and date of birth carry over as-is. Clients without an associated organization link land as standalone Person records. Owner resolution maps My Practice Now practitioner IDs to Pipedrive users by email match.

My Practice Now

Appointment

maps to

Pipedrive

Activity

1:1
Fully supported

My Practice Now appointments map to Pipedrive Activities with type='Meeting' or type='Call' depending on the appointment format. The appointment duration, status (completed/cancelled/no-show), and service type are stored as custom fields on the Activity since Pipedrive Activities have no native duration or service-type fields. Original start time and end time are preserved as the Activity's start and end timestamps.

My Practice Now

Appointment Status

maps to

Pipedrive

Activity Status (custom field)

1:1
Fully supported

My Practice Now appointment statuses (Scheduled, Completed, Cancelled, No-show, Rescheduled) have no direct Pipedrive Activity equivalent. We create a custom pick-list field Appointment_Status__c on Pipedrive Activities to preserve the full status history. Cancelled appointments migrate as completed activities with status Cancelled for audit trail continuity.

My Practice Now

Invoice

maps to

Pipedrive

Custom Invoice Object

1:1
Fully supported

Pipedrive has no native invoice object. We create a custom Invoice object in Pipedrive and migrate invoice header fields (invoice number, issue date, due date, total amount, status) as custom fields. Invoice line items are stored as a JSON-encoded custom field or a related custom Line_Item object depending on the number of line items per invoice.

My Practice Now

Invoice Line Item

maps to

Pipedrive

Invoice Line Items (custom field or related object)

1:1
Fully supported

Invoice line items from My Practice Now (service description, quantity, unit price, tax, total) are encoded as a custom text field on the custom Invoice object. For invoices with complex multi-line structures, we create a related Line_Item custom object linked by a foreign key to the Invoice record, preserving service descriptions and amounts.

My Practice Now

Payment

maps to

Pipedrive

Deal Update or Payment (custom field)

many:1
Fully supported

My Practice Now payments are associated with invoices. When a client has an active or completed service deal in Pipedrive, the payment amount is recorded as a custom field Payment_Received__c on the linked Deal. For standalone payments not tied to a deal, we create a custom Payment record linked to the Person. Payment method (credit card, cash, insurance) maps to a custom pick-list field.

My Practice Now

Custom Intake Field (per client)

maps to

Pipedrive

Custom Field on Person

1:1
Fully supported

My Practice Now custom intake fields vary by practice — common examples include Insurance Provider, Referral Source, Emergency Contact, Diagnosis Codes, and Treatment Notes. We map each custom field to a Pipedrive custom field on the Person object using the same field type (text, pick-list, date, number). Pipedrive's 25-field per object limit may require grouping non-critical fields or using a custom Intake_Details__c text field for less-used data.

My Practice Now

Service / Session Type

maps to

Pipedrive

Custom Field on Activity

1:1
Fully supported

My Practice Now service types (Initial Consultation, Follow-up, Telehealth, Group Session, etc.) map to a custom pick-list field Service_Type__c on Pipedrive Activities. We create the pick-list values in Pipedrive matching the source service types before migration. Any service types not yet configured are flagged for admin review before the full run.

My Practice Now

Client Notes / Clinical Notes

maps to

Pipedrive

Note on Person

1:1
Fully supported

Client notes from My Practice Now migrate as Pipedrive Notes attached to the corresponding Person record. The note body preserves the original content, creation timestamp, and the creating practitioner (mapped to a Pipedrive user by email). Rich-text formatting is simplified to plain text during migration to ensure compatibility with Pipedrive's Note model.

My Practice Now

Insurance Claim

maps to

Pipedrive

Custom Field on Person or Deal

1:1
Fully supported

Insurance claim status (Submitted, Approved, Denied, Pending) and insurance carrier information have no native Pipedrive equivalent. We create a custom Insurance_Claim__c custom field on the Person record and a related Insurance_Details__c section for carrier, policy number, and claim status. Claim amounts can be linked to invoice records for financial reporting.

My Practice Now

Document / File Attachment

maps to

Pipedrive

File on Person or Deal

1:1
Fully supported

My Practice Now file attachments (intake forms, signed consent documents, insurance cards) are re-uploaded to Pipedrive as Files attached to the corresponding Person record. File size limits in Pipedrive (default 25MB per file) are enforced during migration; files exceeding this threshold are flagged for manual re-upload. Inline images in documents are extracted and hosted separately.

My Practice Now

Practitioner / Staff User

maps to

Pipedrive

Pipedrive User

1:1
Fully supported

My Practice Now practitioner and staff records map to Pipedrive Users. Resolution is by email match — each My Practice Now user with a valid email address is mapped to the corresponding Pipedrive user account. Users in My Practice Now without Pipedrive accounts are flagged before migration; they must be invited to Pipedrive or their records assigned to a fallback owner.

My Practice Now

Recurring Appointment / Recurring Session

maps to

Pipedrive

Activity Series (custom field) or Individual Activities

1:many
Fully supported

My Practice Now recurring appointments (weekly, biweekly, monthly series) are expanded into individual Pipedrive Activity records. A custom field Recurring_Series_ID__c links all activities belonging to the same series, preserving the recurrence pattern as a reference. Individual activity records maintain their own start/end times and status.

My Practice Now

Billing / Subscription Plan

maps to

Pipedrive

Custom Field on Person

1:1
Fully supported

My Practice Now billing plans and subscription tiers map to a custom pick-list field Billing_Plan__c on the Person record. If My Practice Now tracks subscription status (Active, Paused, Cancelled), a separate Subscription_Status__c pick-list field captures this. Any pro-rated billing amounts map to custom currency fields for financial reconciliation.

My Practice Now

Waitlist / Prospective Client

maps to

Pipedrive

Lead

1:1
Fully supported

My Practice Now waitlist entries and prospective clients without a confirmed appointment are mapped to Pipedrive Leads. Lead fields (name, email, phone, source) are populated from the My Practice Now waitlist record. A custom field Original_Status__c preserves the waitlist or prospect status from My Practice Now for future segmentation.

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

Pipedrive logo

Pipedrive gotchas

High

Custom field hash keys differ per account

High

Export access gated by visibility groups

Medium

Token-based API rate limits since December 2024

Medium

Sequences and Automations not exposed via REST API

Low

Cost escalates via workflow caps and add-ons

Pair-specific challenges

  • Pipedrive's 25 custom field per object limit may truncate My Practice Now intake fields

    Pipedrive enforces a hard cap of 25 custom fields per object (People, Organizations, Deals). My Practice Now practice setups with 20+ custom intake fields per client will exceed this limit. FlitStack surfaces all custom fields before migration and works with your admin to prioritize the most critical fields for migration. Lower-priority fields are JSON-encoded into a single overflow custom text field (Intake_Data__c) that preserves the full data set for reference even if it cannot be used in Pipedrive's native filters and workflows.

  • Invoice and billing data requires a custom object that My Practice Now does not export natively

    My Practice Now invoice records and payment history have no direct Pipedrive equivalent. Pipedrive has no native invoice module — invoices must be reconstructed as a custom Invoice object with line items encoded as a JSON text field or split into a related custom Line_Item object. The invoice-to-deal linkage (attaching payments to Pipedrive Deals) requires manual configuration of which Deal represents each client's service engagement. FlitStack delivers a pre-migration invoice mapping plan specifying the Deal structure and custom object schema so Pipedrive admins can configure it before data lands.

  • Appointment-to-Activity mapping preserves status but loses calendar-native recurrence

    My Practice Now recurring appointments (weekly, biweekly, monthly series) are expanded into individual Pipedrive Activity records. While each Activity carries the original date, time, and duration, the recurrence pattern is not natively preserved in Pipedrive's Activity model. We link all activities from the same series using a Recurring_Series_ID__c custom field, but Pipedrive's calendar view will show each occurrence as a standalone Activity rather than a recurring series. Practices relying on My Practice Now's calendar-native recurrence features will need to re-establish recurring appointment rules in Pipedrive's calendar integration (Calendly or native calendar sync).

  • Pipedrive API v2 rate limits introduced in December 2024 affect bulk migration throughput

    Pipedrive's token-based API rate limits (introduced December 2024) cap the number of API requests per minute per token. Large My Practice Now migrations with 50,000+ records and hundreds of custom fields will be throttled by these limits during the migration run. FlitStack uses batched API calls with exponential backoff to respect Pipedrive's rate limit tiers (Essential: 60 req/min, Advanced: 120 req/min, Professional and above: higher tiers). Migration clock time extends accordingly — teams should plan for 24–48 additional hours on large record volumes due to rate-limit pacing.

  • Client-to-Organization linkage is lost when My Practice Now has no referring organization

    My Practice Now's client model does not include a separate organization/company object — clients are individuals. Pipedrive separates People (individuals) and Organizations (companies). Client-only records from My Practice Now land as standalone Pipedrive Person records without an Organization link. Any referring organizations recorded in My Practice Now custom fields are migrated to a custom field (Referring_Organization__c) rather than as a Pipedrive Organization record, which limits Pipedrive's reporting on organization-level pipeline views. Teams that track referring practices or corporate clients should pre-create Pipedrive Organization records for those entities before migration.

Migration approach

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

  1. Audit My Practice Now data export and inventory custom fields

    FlitStack connects to My Practice Now via API or CSV export and inventories all client records, appointment activities, invoices, payments, practitioners, and custom intake fields. We identify orphaned records, missing required fields for Pipedrive mapping, and records that will require custom field creation. You receive a written data audit report listing record counts per object, custom field inventory, and any data quality issues (duplicate emails, missing owners) before we proceed with mapping or schema setup.

  2. Create Pipedrive custom object and field schema

    Before data is moved, your Pipedrive admin (or our team) creates the custom Invoice object, custom fields on Person (Insurance_Provider__c, Appointment_Status__c, Service_Type__c, etc.), and custom fields on Activity (Duration_Minutes__c). We deliver a Pipedrive setup plan specifying which custom fields are required per object, their types, pick-list values, and the custom Invoice object structure. Pipedrive's 25-field per object limit is flagged at this stage if your My Practice Now setup exceeds it — you decide which fields to prioritize.

  3. Resolve practitioners and staff to Pipedrive users by email

    FlitStack matches My Practice Now practitioner and staff records to Pipedrive users by email address. Users with no Pipedrive account are flagged with the practitioner name and email for your team to invite before migration. Records belonging to unmatched practitioners are assigned to a designated fallback owner. No data is migrated until owner resolution is confirmed — this prevents records landing in Pipedrive with null owner IDs.

  4. Sequence and run a sample migration with field-level diff

    We migrate a representative sample — typically 100–500 records spanning clients, appointments, invoices, and custom fields — before committing the full run. The sample validates appointment-to-activity mapping (status, type, duration), invoice-to-custom-Invoice-object mapping, practitioner owner resolution, and any custom field value mapping. We generate a field-level diff report comparing source values to destination values so you can verify mapping accuracy before the full migration runs.

  5. Execute full migration with delta-pickup and audit log

    The full migration runs against Pipedrive using API v2 with rate-limit-aware batching. A delta-pickup window of 24–48 hours captures any records created or modified in My Practice Now during the cutover window. FlitStack maintains a full audit log of every record created, updated, or skipped during migration. One-click rollback reverts all migrated data if reconciliation fails. After migration, we deliver a reconciliation report comparing record counts and field totals between My Practice Now and Pipedrive for your team to validate.

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
Pipedrive logo

Pipedrive

Destination

Strengths

  • Intuitive drag-and-drop pipeline that sales reps actually use without resistance or training overhead.
  • Per-seat unlimited-deals model on all tiers — reps cannot be blocked from logging activity.
  • Active marketplace with 400+ integrations and a documented REST API with OpenAPI 3 specs.
  • Mobile apps with offline access, call logging, and calendar sync keep field teams operational.
  • Strong focus on sales activity tracking — next-action reminders and follow-up scheduling are first-class features.

Weaknesses

  • No custom objects — teams needing non-standard data structures must work around the four standard entity types.
  • Workflow automation limits by tier (30, 60, 90 active workflows) force upgrades as processes grow.
  • No free permanent plan — teams evaluating fit must commit to a trial without a freemium option.
  • Limited advanced reporting and custom dashboard capabilities compared to HubSpot or Salesforce.
  • Export permissions are gated by visibility groups, meaning data scoping must account for who can see what before migration.

Complexity grading

How hard is this migration?

Standard CRM migration. 3 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 Pipedrive.

  • Object compatibility

    B

    3 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 Pipedrive 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 Pipedrive data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most My Practice Now to Pipedrive migrations complete in 48–72 hours for under 10,000 records including client data, appointment history, and custom intake fields. Larger practices with 50,000+ records or setups that require a custom Invoice object and extensive custom field creation extend to 5–10 days. Pipedrive API v2 rate limits introduced in December 2024 pace bulk writes on larger datasets, adding several hours to the migration run. The pre-migration data audit and Pipedrive schema setup add 1–2 days before the migration clock starts.

Adjacent paths

Related migrations to explore

Ready when you are

Move from My Practice Now.
Land in Pipedrive, 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