Migrate from Leadforce CRM to Twenty CRM

Leadforce Leads map to Twenty Persons (the standard CRM contact object). Standard fields (name, email, phone, source, status, owner) map directly to Twenty's Person fields. Custom fields on Leadforce Leads are enumerated during the manual UI discovery session and mapped to Twenty custom fields on the Person object, with data type transformation applied where Leadforce field types differ from Twenty equivalents.

Leadforce Deals map to Twenty Opportunities. The deal name, monetary value, stage, and owner assignment transfer directly. Leadforce's deal stage names (which may be custom text values like 'Proposal Sent' or 'Negotiation') migrate as custom OpportunityStage field values rather than requiring Twenty pipeline reconfiguration, since the stage label vocabulary often differs between the two platforms.

Leadforce Activities (calls, emails, meetings, tasks linked to Leads or Deals) map to Twenty Activities. We preserve activity type, timestamp, owner, and linked Person or Opportunity reference. Chronological ordering is maintained by setting the Twenty Activity timestamp to the original Leadforce creation date. Activity type mapping uses Twenty's standard activity type taxonomy.

Leadforce Notes attached to Leads or Deals migrate to Twenty Comments linked to the corresponding Person or Opportunity. We preserve the note body text, creation timestamp, and author attribution. Rich-text formatting is converted to plain text where the source format is not natively supported in Twenty's comment model.

Attachments linked to Deals or Leads require separate file extraction from the Leadforce export package, file naming against the corresponding record ID, and re-upload via Twenty's REST API. We map the attachment foreign key from Leadforce to the target Twenty Person or Opportunity ID and preserve original filenames and MIME types. If Leadforce stores attachments in a format Twenty's API does not accept directly, we convert to a supported format during transformation.

Leadforce does not always use a separate Companies object; company data frequently lives within Lead records. We normalize company fields extracted from Leadforce Leads into Twenty Company records during field mapping, creating Company records first so that the Person-Company relationship is resolved before Person import. Website, industry, size, and address fields map directly where field names align.

Leadforce Proposals generated from Deals contain line items and pricing that do not have a native Twenty equivalent. We export Proposals as structured CSV records and reconstruct them in Twenty either as file attachments (PDF) linked to the parent Opportunity, or as a custom Proposal object defined during schema design if the customer has sufficient Twenty edition support for custom objects.

Invoice records in Leadforce link to Deals and contain payment status and line items. We preserve invoice data as Deal-associated financial records, mapping payment status to a custom Opportunity field (invoice_status__c) and attaching the invoice PDF file to the Opportunity. For customers requiring full invoice history reconstruction, we define a custom Invoice object during schema design.

Leadforce deal pipeline stage names and their sort order migrate as custom fields on the Opportunity object (deal_stage__c, deal_stage_order__c). We do not automatically reconfigure Twenty's standard pipeline stages because Twenty's pipeline model operates at the workspace level and stages are defined through its UI. We provide a written stage mapping table for the customer's admin to apply in Twenty's pipeline configuration after migration.

Leadforce Owner and user assignments on Leads and Deals map to Twenty workspace Users. We perform owner lookup by email match against Twenty's user table. Any Leadforce owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision before the import phase resumes, since OwnerId references are required on most standard objects.

Leadforce supports custom fields on Leads and Deals. We audit custom field schemas during a guided screen-share session where the customer walks through the field creation UI, and we generate a field mapping spreadsheet from the discovered schema. Custom fields are pre-created in Twenty before any data import begins, with Salesforce-style __c API naming if the customer's instance uses a developer naming convention.