Migrate from LeadMaster to Twenty CRM

LeadMaster Accounts (primary company/organization records) map directly to Twenty CRM Company records. The primary contact link migrates as a Person-Company relation. All standard address fields, custom properties, and the original LeadMaster account owner assignment preserve. We resolve the owner by email match against Twenty workspace members at migration time.

LeadMaster Leads are the core object of the source data model. We map them 1:1 to Twenty Person records. The lead status, source, lifecycle fields, and owner assignment all transfer. Note that Twenty CRM has no native Lead-to-Opportunity conversion feature (as documented in GitHub issue #10422); we flag this gap during discovery and document the manual conversion step or custom automation needed post-migration to move Person records into Opportunity pipeline stages.

LeadMaster Opportunities map to Twenty CRM Opportunity records. Stage, amount, close date, owner, and associated Account (Company) link transfer. Custom pipeline stages from LeadMaster are mapped against Twenty's stage list during import. The Opportunity-Company and Opportunity-Person relationships resolve at migration time using company domain or contact email as the lookup key.

LeadMaster Cases (customer support/helpline module) map to a Twenty CRM custom object named Case. We pre-create the Case object and its fields via Twenty's /metadata API before migration: case number, status, priority, description, and the associated company/person link. Conversation threads migrate as Task or Note records attached to the Case.

LeadMaster's custom form builder stores field definitions separately from submitted response data. We extract both during export. Custom form fields that have no direct equivalent in Twenty's schema are pre-created as custom fields on the target object (Person or Company) via the metadata API. For form fields with no viable schema mapping, we fall back to a structured JSON custom field or a rich-text notes field to preserve the data.

LeadMaster marketing campaigns and associated email sends migrate as campaign records with Person associations. Email content and templates export from LeadMaster and are re-imported as Note records or attached documents. Campaign automation sequences (workflow-triggered email sequences) do not migrate; we document the sequence structure for rebuild as Twenty Workflow filters.

LeadMaster landing page templates and form integrations are documented during discovery. The page content exports; the hosting and form-to-lead routing cannot be replicated in Twenty CRM because Twenty does not include a native landing page builder. We deliver a list of every landing page with its form fields and routing logic so the customer's team can re-establish the pages in a dedicated marketing platform or rebuild them in a CMS post-migration.

LeadMaster users, roles, and permission levels map to Twenty workspace members. We match by email address. Active/inactive status preserves. Owner assignments on leads, opportunities, and cases migrate by resolving the LeadMaster user ID to the Twenty workspace member email.

LeadMaster notes, logged calls, email activity, and calendar events migrate to Twenty Task and Event records. Emails migrate as Note records with rich-text body. Call duration, disposition, and recording references transfer to custom fields on the Task. Activity timestamps preserve for timeline ordering. We map to Twenty's standard Task and Event objects using the /graphql endpoint with batch chunking for large activity volumes.

LeadMaster Smart Queues and saved searches define dynamic record filters. These have no direct equivalent in Twenty CRM. We document each Smart Queue as a written specification with its filter criteria, then provide a mapping table showing which Twenty list views or segment filters each Smart Queue should produce post-migration. The customer's admin configures the equivalent views in Twenty.

File attachments stored against leads, accounts, or cases in LeadMaster export and re-upload to Twenty. LeadMaster stores files in Azure; we download each attachment, validate file integrity, and attach it to the corresponding Company, Person, or Opportunity record. Large-volume attachment exports require Azure file access credentials and may extend the migration timeline.