Migrate from FRONTU to Twenty CRM

Frontu company records map directly to Twenty's Companies object. Company name, domain, and address fields translate straightforwardly. Parent-child company hierarchies in Frontu map to Twenty's parentCompanyId relation — the parent record must be imported before child records so foreign keys resolve correctly.

Frontu contact records become Twenty People objects. First name, last name, email, phone, job title, and address fields map to their Twenty equivalents. The contact's primary company links via companyId — Twenty requires the Company record to exist first so the relation can be established during import.

Frontu supports N:N contact-to-company associations natively. Twenty's People object links to one primary Company via companyId. We migrate the most recently associated company as the primary link and surface additional company associations as custom relation fields for admin review and manual cleanup.

Frontu task records map to Twenty Opportunities when they represent billable or trackable work items. Task name becomes Opportunity name. Task status values (Open, In Progress, Completed) map to Twenty Opportunity stage values — we apply a default stage progression but you define which stages represent your pipeline. Closed or archived tasks can optionally filter out of the migration scope.

Non-billable task records such as internal to-do items, checklist steps, and administrative follow-ups migrate as Twenty Task objects. Task name, description, due date, and assignee translate directly. Status values including Pending and Done map to Twenty's task completion model, ensuring workflow continuity after cutover.

Frontu task assignee fields resolve to Twenty WorkspaceMember records by email address match. Unmatched assignees are flagged before migration — your team either creates the Twenty user first or assigns records to a fallback WorkspaceMember. No record lands without a valid assignee in Twenty.

Frontu's Low/Medium/High priority values have no direct equivalent on Twenty's Opportunity object. We create a Priority__c custom select field on Opportunity during schema setup, migrate all original priority values, and configure the same pick-list options so your reporting filters remain intact in Twenty.

Frontu task status values (Open, In Progress, On Hold, Completed, Cancelled) map to Twenty Opportunity stage values by explicit value mapping. The specific stage names are defined in your migration plan — we preserve the original status values so pipeline reports reflect historical state.

Frontu notes and comments attached to tasks or contacts migrate as Twenty Notes, preserving the note body text, original author, and creation timestamp. Rich-text formatting is converted to plain text to ensure consistent rendering in Twenty's note display without HTML artifacts or styling inconsistencies.

File attachments on Frontu task or contact records store as URLs or binary blobs. Twenty does not have a native file attachment storage system equivalent to Salesforce Files. We preserve file URLs as custom text fields on the related record and flag files that require manual re-upload to your chosen Twenty storage integration.

Frontu custom fields on any object — tasks, contacts, or companies — require a matching custom field to be pre-created in Twenty Settings → Data Model before import runs. We audit your full Frontu field inventory, generate the field creation list for Twenty, and validate that all target fields exist before the migration batch starts.

Frontu users who own task records resolve to Twenty WorkspaceMembers by email address match. Users without a matching email in Twenty are flagged before migration. You create the missing WorkspaceMember in Twenty Settings → Members, then we run a second-pass assignee resolution before the final import.