Migrate from Profi to Pipedrive

Profi clients map directly to Pipedrive Persons. Client name, email, phone, address, and social links become Pipedrive Person fields. A client with no associated organization maps as a standalone Person; no AccountId link is required unless the client also exists as a business entity.

If a Profi client record includes a company name or business affiliation, that organization maps to a Pipedrive Organization record. The Person-Organization link is created via Pipedrive's relationship model after both records exist. Multi-client organizations in Profi (multiple clients linked to one company) resolve to one Organization with multiple linked Persons.

Each Profi session booking (one-on-one, group, consultation) becomes a Pipedrive Activity of type 'Meeting' or 'Call' linked to the Person record. Session type (one_on_one, group, consultation) maps to the Activity's Subject line or a custom Activity Type field. The original session date and time become the Activity's start and end timestamps, preserving the engagement history on the Person record.

Each active Profi package enrollment maps to a Pipedrive Deal. The package name becomes the Deal name; the package fee becomes the Deal Amount. Enrollment date maps to Deal Create Date; package expiry date becomes a custom field (Package_Expiry__c). The Deal's Person link connects the service offering to the client record. Multiple concurrent packages per client create multiple Deals, linked to the same Person.

Profi package tiers (e.g., Starter, Growth, Enterprise) have no native Pipedrive equivalent. We create a custom pick‑list field Package_Tier__c on the Deal object and map each Profi tier value value‑by‑value, preserving the exact label semantics. This enables package‑level segmentation in Pipedrive's reporting views, allowing teams to filter deals by tier and analyze revenue distribution across coaching programs.

Profi session status values (scheduled, completed, cancelled, no_show, rescheduled) have no direct Pipedrive Activity field. We create a custom pick-list field Session_Status__c on Pipedrive Activities and map each status value individually. Cancelled sessions migrate with their original timestamp but marked as cancelled for historical reporting.

Profi's content rooms and course enrollment links are not a native Pipedrive construct. We migrate course access status (active, completed, revoked) and course URLs as text or pick-list custom fields on the Person record. Completion percentages or drip-delivery progress require a custom number or text field since Pipedrive has no native content-progress tracking.

Profi's recurring session patterns (weekly, biweekly, monthly) are stored as scheduling metadata. Pipedrive does not have a native recurring-activity engine at the session level. We preserve the recurring pattern as a custom text field Recurring_Schedule__c on the Activity or Person record for reference. Pipedrive Automations can be configured post-migration to replicate recurring follow-up tasks, but the original pattern itself is informational only.

Profi client journal entries and coaching notes map to Pipedrive Notes attached to the Person record. Original timestamps and author information are preserved. If notes contain rich formatting, Pipedrive Notes support basic formatting and are attached to the Person entity at the correct create date.

Profi coaches (owner assignment on client records) are resolved by email address against Pipedrive Users. If a coach email matches an existing Pipedrive User, the Person and Deal OwnerId fields are set automatically. If no match is found, the record is flagged before migration for your team to assign to the correct Pipedrive User or invite the coach as a new User.

Files attached to Profi client records or session bookings (e.g., session handouts, signed agreements) are downloaded and re-uploaded as Pipedrive Activity attachments or Person attachments. Pipedrive's file size limit applies (25MB per file for the standard plan). Files larger than this are flagged for manual handling.

Profi custom fields at the client level (e.g., referral_source, coaching_focus_area, membership_start_date) map to Pipedrive Person custom fields. Field types are matched (text, number, date, pick-list) and the custom field is created in Pipedrive before migration with the identical name or a mapped equivalent. Multi-option Profi fields map to Pipedrive multi-select fields.