Migrate from Profi to Twenty CRM

Profi clients map directly to Twenty People records. The client's name, email, phone, and address fields translate 1:1. Note that Twenty People records require a name field — clients without a full name are imported with the available display name and flagged for review.

If Profi clients include an organization or business name separate from their personal name, that value maps to a linked Company record in Twenty via the companyId relation. The Company record must be created first (import order: Companies → People) so the foreign-key resolves correctly during CSV import.

Individual coaching or service sessions map to Twenty Tasks. The session date and time map to the Task due date; the session duration maps to a custom field or the task description. The Task is linked to the corresponding People record via the People-Task relation. Owner assignment is resolved by email match against Twenty workspace members.

Session notes, summaries, and coach observations map to Twenty Notes attached to the relevant People record. The original session date is preserved in the Note body or a custom datetime field. This approach keeps the session timeline intact in Twenty without creating task clutter for historical sessions.

Profi packages (bundles of sessions sold as a unit) map to Twenty Opportunities. The package price maps to Opportunity amount; the package status maps to Opportunity stage (e.g., 'Active' → 'In Progress', 'Completed' → 'Closed Won'). If a package spans multiple sessions, individual session Tasks are linked to the parent Opportunity via a custom Opportunity-Task relation field.

Packages with N sessions that need granular tracking are split: the package becomes an Opportunity, and each session within the package becomes a record in a custom SessionRecord object linked to the Opportunity. This preserves per-session data while maintaining the package-level deal value for pipeline reporting.

Profi billing records (invoice ID, payment status, amount paid) have no native equivalent in Twenty's CRM model. We preserve these as a custom fields on the Opportunity record (Invoice_ID__c, Payment_Status__c, Amount_Paid__c). Recurring billing configuration must be rebuilt using Twenty's workflow builder or a third-party billing integration.

Any Profi custom fields (e.g., 'Coach Rating', 'Session Type', 'Referral Source') are migrated as Twenty custom fields. Twenty requires fields to be created in Settings → Data Model before CSV import — we deliver a field-creation checklist as part of the migration plan so your workspace is ready before data lands.

Profi owner and coach IDs are resolved by email match against Twenty Workspace Members. If a Profi owner has no corresponding Twenty user, their records are assigned to a default owner and the unmatched mapping is surfaced in the pre-migration report for your team to resolve.

Profi engagement notes (messages, call summaries not tied to a session) migrate as Twenty Notes attached to the relevant People record. Original timestamps and the creating user's email are preserved in custom fields on the Note for audit continuity. This includes any ad-hoc communications logged by coaches or clients outside of scheduled sessions, ensuring that all historical context transfers even when no formal session record exists in the source system.

Profi file attachments are preserved as URLs in a custom text field (File_URL__c) on the relevant record. If the attachment is a document (contract, intake form), we recommend re-uploading it to your preferred cloud storage and linking the URL — Twenty's CSV import does not support binary file ingestion.