Migrate from Profi to Salesforce Sales Cloud

Profi clients map 1:1 to Salesforce Contacts. The challenge is that Salesforce requires an AccountId lookup on every Contact — Profi's clients may not have an associated company. We create Account records for each client or link them to a specified Account based on your rules before the migration runs.

Profi coach and staff accounts map to Salesforce Users. Role and profile assignment follows your specification — coaches typically get Sales rep or custom profile. Unmatched users are flagged before migration so you can invite them to Salesforce first or assign a fallback owner.

Profi sessions migrate as Salesforce Events. The original session title becomes Subject, coach assignment becomes OwnerId (via email match), start/end times preserve as StartDateTime and EndDateTime. Notes and descriptions carry over as Event Description. Multi-client sessions require a decision point covered in the gotchas section.

Profi courses have no direct Salesforce equivalent. We migrate course metadata (title, description, enrollment count, status) to a custom Course__c object. If you use Salesforce CPQ for subscription renewals, courses map to the standard Product object with custom fields for enrollment data instead.

Profi enrollment records link a client to a course with status and enrollment date. These merge into a custom Course_Enrollment__c junction object with lookup fields to Contact and Course__c (or Product). This preserves the many-to-many relationship that Profi handles natively.

Profi billing records (amount, date, status, associated client) map to a custom Invoice__c object with Contact and AccountId lookups. If amounts represent course purchases tied to renewal tracking, they map to Opportunities instead. Full accounting records should be reviewed post-migration as Salesforce is not a bookkeeping tool.

Profi notes on clients, sessions, or courses migrate as Salesforce Notes (modern Notes object, not legacy Note). The note title, body, and associated record link (Contact, Event) carry over. Owner resolves by email match to Salesforce User. Files attached to the note re-upload as Salesforce Files linked to the parent record.

Files attached to Profi records (session recordings, course materials, client documents) re-upload to Salesforce Files. Files are linked to the parent record (Contact, Event, Course__c). Salesforce file size limits (25MB default per file) apply — large video files may need alternative storage with a link stored on the Salesforce record.

Every Profi custom field requires a corresponding Salesforce custom field created before migration. We generate a field creation checklist specifying the field name, Salesforce API name (__c suffix), data type, and picklist values. Your Salesforce admin creates these fields in Setup — this is a manual step that gates the migration start date.

Profi stores coach-client associations natively. In Salesforce, Users and Contacts have no native many-to-many relationship. We create a custom Coach_Assignment__c junction object linking User (coach) to Contact (client), with fields for assignment date and relationship type. Your admin chooses whether to recreate all assignments or apply a default.

Profi assigns records by user email. We match Profi user emails against Salesforce User emails to resolve OwnerId on Events and Contacts. Unmatched owners are flagged before migration with two options: invite the user to Salesforce first or assign to a fallback user. No record lands without an owner.