Migrate from coreplus to Pipedrive

CorePlus client records map 1:1 to Pipedrive People. Each client becomes a Person with name, email, phone, address, and custom fields. Clients without an email receive a placeholder or are flagged for manual review before migration. Practitioner ownership resolves by email match to Pipedrive Users.

CorePlus practitioner records map to Pipedrive Users by email resolution. Practitioners who are also sales reps in Pipedrive receive their existing user records; practitioners who are not Pipedrive users have their records assigned as activity owners or remain as custom Person fields. Supervisor-level practitioners in CorePlus are flagged for admin role assignment in Pipedrive.

Referrers in CorePlus (referral sources, partner clinics, referring physicians) map to Pipedrive Organizations. The referrer's name, contact details, and referral-source classification migrate as Organization name and custom fields. Referral-source type becomes a Pipedrive label on the Organization record. We apply the referrer-type value mapping to Organization labels, and flag referrers without email for the team to decide whether to create placeholder Organizations or collapse these referrals into a generic 'Direct' organization.

CorePlus appointments map to Pipedrive Activities — appointments with a scheduled duration become Events (meetings/calls) with start and end times; single-point appointments become Tasks with a due date. The assigned practitioner becomes the Pipedrive Activity owner. Original appointment status (confirmed, cancelled, no-show) is preserved as a custom field or Activity label.

CorePlus service types (the types of sessions or consultations offered) have no direct Pipedrive equivalent. We create Pipedrive custom fields (single-option or multiple-option depending on whether clients can have multiple service types) on Person records. Service type labels are preserved verbatim as custom field options. Fee information for service types maps to Pipedrive Products if the team uses Pipedrive's product catalog.

CorePlus invoices and draft notes map to Pipedrive Deals. The invoice amount becomes the Deal value (Amount field). Invoice status (paid, outstanding, draft) maps to a custom Deal field or a Pipedrive label. Line items from invoices map to Deal Products if the team uses Pipedrive's product catalog. Note that Pipedrive has no native invoice management — billing records are approximated in the Deals model.

CorePlus client groups (used to categorize clients by program, location, or service tier) map to Pipedrive Labels on Person records. Teams can alternatively map client groups to Organizations if the groups represent referring entities. We surface both options in the mapping plan and let the team choose before migration runs.

CorePlus availability slots are scheduling constructs with no Pipedrive equivalent. Pipedrive does not have native availability or scheduling management (Calendly integration is available on Advanced+ plans). Availability slots are not migrated; the team rebuilds scheduling in Pipedrive via Calendar Sync or an external scheduling tool.

The CorePlus instant data backup produces a CSV with client details including all structured fields. This CSV is ingested as the primary source for Person records. Practitioner assignments and service types in the CSV are cross-referenced against practitioner and service-type endpoints to enrich the migration with owner and custom field data.

CorePlus's MYOB export function generates text files for import into MYOB accounting software. This export format has no direct Pipedrive equivalent. We preserve the MYOB export data as a reference file; the team rebuilds accounting integration separately via Pipedrive's accounting integrations or native MYOB connector if available.