Migrate from Teamleader to Salesforce Sales Cloud

Teamleader has no separate Lead object — all prospects live as Contacts. We split Teamleader Contacts into Salesforce Lead (unqualified) and Contact (qualified, attached to an Account) based on a rule defined during scoping: typically, Contacts with no associated Deal or with a pipeline stage before 'Proposal Sent' become Salesforce Leads; those with active Deals or a closed-won status become Contacts. We preserve the original Teamleader contact ID in a custom field tl_contact_id__c on both Lead and Contact for audit and cross-reference.

Teamleader Company records map to Salesforce Account. The Company website becomes the Account Website field and serves as the dedupe key. We use Company.tl_id as an External ID field on Account so that during Contact import, the AccountId lookup resolves automatically rather than requiring a separate resolution pass. Account is migrated before Contact so the lookup is satisfied at insert time.

Teamleader Deals map to Salesforce Opportunity. The Deal's pipeline and stage map to a Salesforce Record Type and Sales Process that we configure before migration. Closed-Lost and Closed-Won dates migrate to Opportunity CloseDate and StageName. Deal value (amount) maps to Amount; currency_code from Teamleader is preserved in a custom field if multi-currency is enabled in Salesforce.

Each Teamleader pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Teamleader's stage names map to Salesforce StageName labels, and probability percentages migrate to StageProbability. On FLOW-tier accounts with unlimited pipelines, each Record Type gets its own Page Layout scoped to the line of business.

Teamleader Projects have no direct Salesforce Sales Cloud standard object. We pre-create a custom Project__c object with fields for Project Name, Start Date, End Date, Status, Budget, and Owner, then migrate Projects as custom records. Projects are sequenced after Account migration so that the AccountId lookup is satisfied. Projects__c does not migrate work-tracking features such as dependencies, Gantt views, or resource allocation — these require a Project Management Cloud (Core, Field Service, or a PSA app) as a separate engagement.

Teamleader Milestones are child records of Projects and carry due dates, budgets, and custom fields. We pre-create Milestones__c with a lookup to Projects__c, migrate Milestones after Projects, and resolve the Project lookup by matching Teamleader's project_id to the Projects__c tl_project_id__c External ID field. The Milestones__c records maintain ordering by the original Teamleader sequence field.

Teamleader Invoices have no Salesforce standard equivalent. We migrate Invoice records as a custom Invoices__c object with fields for Invoice Number, Invoice Date, Due Date, Total Amount, Status, Line Items (as a long-text summary), and Company lookup to Account. The 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 explicitly in the migration handoff so the customer can reactivate reminders in Salesforce or their chosen billing tool.

Teamleader Subscriptions represent recurring billing relationships with periodicity and pricing. We migrate them as Subscriptions__c with fields for Subscription Name, Account lookup, Start Date, End Date, Recurring Amount, Billing Frequency, and Status. Custom fields on Subscriptions use Teamleader's 'subscription' context and are enumerated during scoping before schema creation.

Teamleader Products map to Salesforce Product2 records, with Standard Price Book entries created during import. ProductCode maps from Teamleader's product code. Price information migrates to PricebookEntry so that OpportunityLineItems can reference it.

Teamleader Quotations (available on GROW and FLOW tiers) map to Salesforce Quote, which is a standard object from Salesforce Professional. Quotation line items map to QuoteLineItem. Expiry dates and margin calculations from Teamleader migrate to Salesforce QuoteExpiryDate and a custom margin field. We attach any linked PDF documents as ContentDocument records on the Quote.

Teamleader Tickets migrate to Salesforce Case if the destination org includes Service Cloud. Ticket status workflows map to Case Record Type and Case Status values. If the destination Salesforce org does not include Service Cloud licenses, we migrate Tickets as a custom Tickets__c object and note the Service Cloud gap in the handoff. Conversation threads migrate as EmailMessage records linked to the Case.

Teamleader Time Entries are logged against Projects or Tasks and may be billable. We migrate Time Entries as Time_Entries__c with a lookup to Projects__c, User (as Owner), Duration, Billable flag, Description, and Work Date. Time Entries do not automatically link to Opportunities or Invoices in Salesforce without custom automation, which is documented as a post-migration admin task.

Teamleader Tasks migrate to Salesforce Task. Task Status, Priority, ActivityDate, and Subject transfer directly. The linked Contact or Deal resolves via the Contact or Opportunity lookup (WhoId and WhatId) using the tl_contact_id__c and tl_deal_id__c External ID fields as resolution keys.

Teamleader Meeting records migrate to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendees resolve to EventRelation records pointing at the matched Leads, Contacts, and Users. We set ActivityDate to the original Teamleader timestamp to preserve timeline ordering.

Teamleader Phone calls map to Salesforce Task with TaskSubtype = Call. Call duration and disposition from Teamleader transfer to custom Task fields. ActivityDate is set to the original Teamleader timestamp. Call recording URLs are preserved in a custom field and are accessible to admins post-migration.

Teamleader Users map to Salesforce User records. We resolve by email match. Any Teamleader Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Teamleader users are mapped to inactive Salesforce Users so historical assignment is preserved.