Migrate from LeadManaging to Twenty CRM

LeadManaging leads map directly to Twenty CRM People records. The name, email, phone, and job title fields carry over as-is. The companyId reference in Twenty requires a Company record to exist first, so Company records migrate before People records in the migration sequence.

LeadManaging's lead status field (New, Contacted, Qualified, etc.) has no direct Twenty CRM equivalent. We migrate it as a custom select field on the People object. If you use multiple status values across teams, a pick-list field handles the translation cleanly.

LeadManaging company records map 1:1 to Twenty CRM Companies. Company name, domain/website, industry, and address fields transfer directly. Multi-location companies in LeadManaging may need to split into multiple Twenty Company records if each location is tracked separately as separate entities.

LeadManaging deals map to Twenty CRM Opportunities. Deal name, amount, expected close date, and stage all have direct Twenty equivalents. Stage pick-list values need value-by-value mapping if your LeadManaging stages differ from Twenty's default Opportunity stages. Additionally, any custom fields attached to the deal will be transferred as custom fields on the Opportunity, provided they have been pre‑created in Twenty's Data Model.

LeadManaging property-leasing stages (Inquiry, Showing, Application, Lease Signed, etc.) map to Twenty's Opportunity Stage values. We map each stage name and probability. If you have multiple deal pipelines in LeadManaging, each pipeline maps to a separate set of Opportunity stages.

LeadManaging call logs and activities with a due-date or follow-up action migrate as Twenty CRM Tasks. The task title, description, assignee, due date, and completion status all carry over. Completed activities preserve the completion timestamp. If an activity lacks a due date but has an assignee, we treat it as a task with a null due date, ensuring no follow‑up actions are lost.

LeadManaging email activity that is informational (not a task) migrates as Twenty CRM Notes attached to the relevant People record. Email subject and body content transfer as the Note title and body. If the email should generate a follow-up task, we create a Task in addition to the Note.

If LeadManaging stores property-specific records as a custom object (e.g., unit listings, showing schedules), we migrate those as Twenty CRM custom objects. The object name and fields transfer, but custom field definitions must be pre-created in Twenty's Settings > Data Model before the import runs.

LeadManaging owner assignments resolve by email match against Twenty CRM workspace members. Users must accept their Twenty invitation before the migration runs — the Twenty documentation explicitly requires this so user relations map during import. Unmatched owners flag for manual assignment before cutover.

LeadManaging notes attached to leads migrate as Twenty CRM Notes on the People record. Rich-text formatting in LeadManaging notes gets converted to plain text or the subset of formatting that Twenty's Note body field supports. Attached files re-upload to Twenty's file storage.

LeadManaging file attachments on leads, companies, or deals re-upload to Twenty CRM. Files attach to the target record (People, Company, or Opportunity) using Twenty's file attachment mechanism. Large files may require chunked upload for PDFs or images over 10MB or other large media.

LeadManaging automations and sequences have no equivalent in Twenty CRM's migration scope. We export your LeadManaging workflow definitions as a structured JSON or PDF reference document that your Twenty admin can use to rebuild equivalent automation logic in Twenty's workflow builder.

LeadManaging reports and dashboards do not migrate. The data that powers those reports — contacts, companies, deals, activity history — transfers completely. Your Twenty admin rebuilds reports using Twenty's built-in analytics after migration. We recommend exporting a snapshot of any custom report definitions before cutover, so the admin has a reference for recreating metrics and visualizations in Twenty.

LeadManaging's lead source field (Website, Referral, Walk-in, etc.) migrates as a custom select field on the People object in Twenty CRM. Source values map pick-list by pick-list unless your LeadManaging plan uses free-text source values, which transfer as text in the custom field.