Migrate from Teleforce CRM to Twenty CRM

Teleforce Contacts map to Twenty People records. Field-level mapping requires pre-creating the Teleforce-equivalent fields in Twenty Settings → Data Model because Twenty ships minimal standard fields (name, email, phone only confirmed). We request the customer's full Teleforce field inventory during discovery and create matching fields before import. Contact owner maps to Twenty workspace Member via email match; the member must be invited and active before owner assignment is set.

Teleforce Companies map to Twenty Companies. Industry, website, employeeCount, and annualRevenue are common Teleforce fields that must be pre-created as Twenty Company fields before CSV column mapping. The Company record is imported before People so that the People-Company relationship (handed via domain match or a foreign key column) resolves at insert time.

Teleforce Deals map to Twenty Opportunities. The dealstage property maps to Twenty pipeline Stage values, which must be pre-created in Twenty Settings → Data Model → Pipelines before import. Closed-Lost and Closed-Won stage mapping is preserved as custom Opportunity fields if the customer used these states in Teleforce. Amount, probability, and close date transfer directly as Opportunity fields.

Teleforce pipeline configuration maps to Twenty Pipelines. Each Teleforce pipeline becomes a Twenty Pipeline with its own stage set. Stage names, order, and probabilities must be explicitly defined in Twenty before Deals reference them. We collect the exact pipeline and stage names from the customer's Teleforce instance during discovery.

Teleforce Leads appear as a distinct lifecycle stage or record type. We map Teleforce Leads to Twenty People records with a custom field original_record_type__c set to Lead for segmentation. The customer chooses whether to keep Leads separate or merge them into existing People records during scoping.

Teleforce call logs from the unified inbox migrate to Twenty Task records with a call-specific subtype. Call duration, disposition, and recording URL transfer to custom Task fields. We extract available call data via CSV; inbox thread-level history may be incomplete if Teleforce's export does not cover it independently.

Teleforce email activity linked to Contacts migrates to Twenty Task records with the original timestamp preserved in ActivityDate. Email body content migrates as Task description if the CSV export includes it; we flag it as partial if the export truncates rich-text content.

Teleforce notes linked to Contacts, Companies, or Deals migrate to Twenty Note records attached via the target record's ID. Note creation timestamp and author information transfer as custom Note fields if available in the export.

Teleforce custom fields on Contacts map to Twenty custom fields on People. The Twenty field must be pre-created in Settings → Data Model before the CSV import column is mapped. Field types are matched: text fields to text, number fields to number, date fields to date, and picklist fields to select options with the same value set.

Teleforce custom fields on Deals map to Twenty custom fields on Opportunity. Same pre-creation requirement applies. We collect the complete custom field inventory from the customer during discovery because no public API or documentation exists to enumerate them automatically.

Teleforce owner assignments on Contacts, Companies, and Deals map to Twenty Members by email match. We require the customer to invite all active owners into the Twenty workspace before migration begins. Any owner without a corresponding Twenty Member is flagged in a reconciliation report and held until provisioned.