Migrate from Teamleader to Twenty CRM

Teamleader Contacts map to Twenty Persons. We use the Teamleader contact.email as the dedupe key during import. The Teamleader contact salutation, first name, last name, phone, mobile, website, language, and tags migrate to their Twenty Person equivalents. Custom fields on the Teamleader 'contact' context enumerate via customFieldDefinitions.list during scoping and map to Twenty custom fields on Person.

Teamleader Companies map directly to Twenty Companies. Company name, VAT number, business identification number, phone, website, address, city, zip, and country migrate. Custom fields on the Teamleader 'company' context enumerate separately from the 'contact' context and map to Twenty Company custom fields. Person-to-Company linkage migrates as a Twenty Relation record.

Teamleader Deals map to Twenty Opportunities. The deal title becomes the Opportunity name, monetary amount migrates directly, expected close date maps to the Opportunity close date, and deal stage maps to a Twenty Opportunity status value. We configure the status values to match the Teamleader Pipeline stages before migration so that the stage mapping is a direct value lookup rather than a transform. Owner resolves by email match to a Twenty workspace User.

Teamleader Pipelines (1 on SMART, 2 on GROW, unlimited on FLOW) map to Twenty Opportunity status values within a single Twenty workspace. Each Pipeline's Stages become distinct status strings. If the customer uses multiple Pipelines to separate lines of business, we create a custom Opportunity field pipeline_name__c in Twenty to preserve that segmentation alongside the status field.

Teamleader Projects have no direct Twenty CRM equivalent because Twenty lacks a native project management module. Small projects with milestone summaries migrate as a custom Project object that we pre-create in Twenty's schema. Alternatively, Project summary and key dates migrate as a Note attached to the primary Opportunity or Company, with the customer choosing the strategy during scoping. Work breakdown structure and sub-task hierarchy are documented in the migration inventory for rebuild in a dedicated project tool (Notion, Asana, Jira).

Teamleader Milestones are child records of Projects with due dates, budgets, and custom fields. When Projects migrate as Twenty custom objects, Milestones migrate as child Task records under the Project custom object. When Projects migrate as Notes, Milestones are appended to the Note body as structured text entries. We resolve the Project reference during import by matching on Project title and Company linkage.

Teamleader Invoices map to a pre-created Invoice custom object in Twenty. Invoice header fields (invoice number, date, due date, total amount, tax amount) migrate directly. Line items migrate as child records or as a JSON blob in a long-text custom field depending on the customer's reporting needs. QR-code payment state, automatic reminder triggers, and overdue flags do not transfer because they are tied to Teamleader's payment processing system; we document this gap in the migration inventory for the customer's admin to address post-migration.

Teamleader Quotations map to a pre-created Quotation custom object in Twenty. The quotation title, total amount, status, expiry date, and margin (on GROW/FLOW) migrate. Line items migrate as a structured text block or child records. Linkage to the originating Deal or Contact migrates as a Twenty Relation or Opportunity lookup depending on the customer's scoping choice.

Teamleader Subscriptions (recurring billing relationships) map to a pre-created Subscription custom object in Twenty. The subscription periodicity, pricing, status, and linked Contact or Company migrate. Custom fields on the Teamleader 'subscription' context enumerate and map during scoping.

Teamleader Products (catalog items used in Quotations, Invoices, and Subscription line items) map to Twenty's product capability if available, or to a pre-created Product custom object. Product name, SKU, unit price, description, and custom fields on the 'product' context migrate.

Teamleader Tickets (support requests with status workflow, assignee, and linked Company or Contact) map to a pre-created Ticket custom object in Twenty. Ticket status, priority, subject, description, assignee, and linked Contact or Company migrate. Custom fields on the Teamleader 'ticket' context enumerate separately. If the customer uses Tickets primarily for pre-sale qualification tracking rather than support, we discuss whether to map them to Opportunities or a custom Qualification custom object.

Teamleader Activities (Tasks, Meetings, Phone calls) map to Twenty Task and Event records. Each activity type migrates with owner, due date or event start/end, linked Contact or Deal, and body text. We resolve the linked Contact or Deal reference by querying Twenty for the matching Person or Opportunity by name or email before inserting the activity record. Phone call disposition and duration migrate to custom Task fields.