Migrate from The Practice to Pipedrive

Each The Practice client record maps to a Pipedrive Person. The client's first and last names concatenate into Pipedrive’s name field, while email, phone, and address fields migrate directly. Any additional contact details stored in The Practice (such as secondary emails or social handles) can be captured as custom fields on the Person. The Practice client ID is stored as Source_System_ID__c on the Person for reconciliation and delta‑run deduplication.

If The Practice records the client’s employer or business, that information becomes a Pipedrive Organization linked to the Person via Pipedrive’s person‑organization association. When a client has multiple affiliations, each business can be created as a separate Organization and linked through relationships. Clients that lack a company entry are imported as Persons without an Organization link, and any orphan relationships are flagged in the pre‑migration QA report for manual cleanup.

An active coaching package in The Practice becomes a Pipedrive Deal. Deal Name uses the client name + package type. Deal Value reflects the remaining session credit or total package price. The Deal is linked to the Person and optionally the Organization.

The Practice package status (e.g., Active, Completed, Paused) maps to a corresponding Pipedrive pipeline stage. We create a stage for each status found in The Practice and map the status string to the stage name via a value‑mapping table. Original status‑change timestamps are stored as custom datetime fields on the Deal. Any status without a Pipedrive equivalent is flagged for manual assignment.

Each The Practice session maps to a Pipedrive Activity. Session type determines the Activity type: coaching sessions become Meetings with start/end times; administrative tasks become Tasks. The session date, duration, and coach assignment are preserved on the Activity, and session notes are written to the Activity’s note field. The Activity is linked to the client’s Person record and to the Deal when applicable to keep each interaction’s context.

The Practice coach assignments resolve to Pipedrive Users by email match. If a coach has no Pipedrive account, records assign to a fallback owner or a dedicated 'Unassigned Coach' user. Unmatched coaches are flagged before migration so your team can provision accounts first.

The Practice intake form responses and client notes migrate as Pipedrive Notes attached to the Person record. Rich‑text formatting is preserved where The Practice exports it. Original create dates and the note author are stored on the Note for audit continuity. If a note includes file attachments, they are uploaded to Pipedrive’s file storage and linked to the Note, keeping supporting documents with the record.

Paid invoices from The Practice do not map to a native Pipedrive object since Pipedrive has no invoice module on base plans. We migrate invoice metadata (amount, date, status) as a Note on the associated Deal and create a 'Payment Received' Activity for each settled invoice.

The Practice custom client fields map to Pipedrive custom fields on Person. Each custom field must be created in Pipedrive first via POST /personFields before migration — we generate the field creation plan and execute it as part of the Pipedrive schema setup step.

The Practice records the channel through which each client discovered the practice (e.g., referral, organic search, paid advertisement). This information maps to a Pipedrive pick‑list field on the Person record. Where source values differ from Pipedrive’s default options, we create pick‑list entries to match the data. Any client records with an unmapped source are flagged in the migration report for your team to update the field or adjust the pick‑list.