Migrate your Profi data

Clients are the primary contact object in Profi. Each client record holds name, email, timezone, and a profile photo. We export client records as structured JSON with all standard fields and map them directly to Contact objects in the destination CRM. Custom client fields are preserved via field-level mapping.

Sessions represent individual coaching appointments booked through Profi's scheduling engine. Each session has a date, duration, status, and a link to the client. We export session records with their timestamps and status flags and create corresponding Task or Event objects in the destination CRM, preserving the client linkage.

Packages bundle multiple sessions or courses under a single purchase. Package definitions include session counts, expiration dates, and pricing tiers. We export package metadata and the enrolled-client linkages, but because package-to-session inheritance is not consistently exposed in exports, we reconstruct the session-credit ledger separately during migration.

Coaches use journal entries to record notes and observations between sessions. Each entry is tied to a specific client and timestamp. We export journal entries as Notes or Custom Note objects, preserving the client association and chronological order.

Courses consist of modules and lessons delivered either live or on a drip schedule. The course structure and enrollment records export cleanly, but video content files require separate file-system export and re-hosting, which we coordinate with the customer during the content migration phase.

Profi provides built-in secure video rooms for one-on-one and group sessions. Room settings and historical room links export as metadata. Active video recordings must be downloaded from Profi's storage before the migration cutover, since they are not exposed via any public export endpoint.

Invoice and payment records live in Profi's billing subsystem. We export invoice line items, payment status, and amounts. Recurring billing relationships tied to Packages are exported as subscription metadata, but the recurring-payment automation does not transfer to the destination platform automatically.

Coaches can define custom fields on the client profile to track niche-specific data. These fields export as name-value pairs. We remap them to equivalent custom fields in the destination CRM, applying type conversion where field types differ, and flag any fields that have no target equivalent for manual review.

Team member accounts include name, role, and scheduling permissions. We export all active team member profiles and map them to User or Member objects in the destination, preserving role assignments and access levels.