Migrate from Teamleader to Microsoft Dynamics 365 Sales

Teamleader Contacts with an associated Company map to Salesforce-style Contact attached to an Account. Teamleader Contacts without a Company association or with a 'prospect' classification map to Dynamics 365 Lead. We apply a classification lookup at migration time using Teamleader's contact type property, and preserve the original Teamleader contact ID in a custom field tl_contact_id__c on both Lead and Contact for reconciliation.

Teamleader Company records map directly to Microsoft Dynamics 365 Sales Account. The Company address, industry, VAT number, and website fields map to Account fields. Account is inserted before Contact import so that the AccountId lookup is satisfied at Contact insert time. Company names serve as the dedupe key during import.

Teamleader Deals map to Dynamics 365 Opportunities. The deal phase (Teamleader stage name) maps to a Dynamics Opportunity Stage; the Teamleader Pipeline maps to a Dynamics Record Type or Sales Process. Closed-Lost and Closed-Won status from Teamleader carry over as Stage values. We flag any Teamleader Deal with a linked Project for the customer to decide whether the Project maps to a custom entity or becomes an Opportunity note.

Each Teamleader Pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process that whitelists the mapped stage values. Probability percentages transfer from Teamleader to Dynamics StageProbability with rounding to the nearest integer. If Teamleader GROW or FLOW is in use with multiple pipelines, we create one Record Type per pipeline in Dynamics.

Teamleader Invoices map to Microsoft Dynamics 365 Sales Order (or a custom Invoice entity if the customer licenses Project Operations or Finance). Invoice line items, tax codes, payment status, and totals migrate. Teamleader's 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 for post-migration reactivation. If the customer uses Teamleader GROW or FLOW for recurring subscriptions, we flag the subscription-to-contract mapping as a separate configuration step.

Teamleader Subscriptions (recurring billing relationships with periodicity and pricing) map to Dynamics 365 Contract or a custom Subscription entity depending on the Dynamics edition licensed. Subscription periodicity, pricing, start date, and status migrate. We flag the contract activation step post-migration because automatic renewal triggers and billing integration require separate configuration in Dynamics.

Teamleader Products define catalog items used in Quotations, Invoices, and Subscription line items. They map to Dynamics 365 Product2 with Standard Price Book entries created during import. ProductCode, unit price, and description transfer directly. If Teamleader products include bundle or package structures, we flatten them to individual Product2 records with a custom bundle_id__c field for the customer's admin to reassemble in Dynamics.

Teamleader Quotations (proposals preceding Deals or Invoices) map to Dynamics 365 Quote. Expiry dates, margin calculations (GROW and FLOW tier), and line items transfer. If the Quote is in Accepted or Expired status, we preserve that status in a custom field tl_quotation_status__c because Dynamics Quote Status is workflow-driven post-migration. Signed Quote PDFs migrate as SharePoint document attachments linked to the Quote record.

Teamleader Tickets representing customer support requests map to Dynamics 365 Case if the destination org includes Dynamics 365 Customer Service or the Case object is active in Sales. Ticket status workflow maps to Case Status; assignee maps to Case Owner. Custom fields on Teamleader Tickets (scoped under the 'ticket' context) map to custom fields on Case.

Teamleader Projects with Milestones have no direct Microsoft Dynamics 365 Sales native equivalent. Sales CRM does not include a project management object. We flag Projects as requiring one of three strategies: (1) map to a custom Project entity created in Dynamics, (2) link to the related Account with project details stored in a custom field, or (3) retain in Teamleader and maintain a read-only sync via Power Automate. The customer selects the strategy during scoping.

Teamleader Milestones (sub-objects of Projects with due dates, budgets, and custom fields) require a destination decision tied to the Project mapping strategy above. If Projects map to a custom entity, Milestones map to a child custom entity. If Projects map to Account notes, Milestones map to Tasks with a custom milestone_flag__c field and a custom project_reference__c lookup.

Teamleader activity records (Tasks, Meetings, Phone calls) map to Dynamics 365 Task and Event. Call disposition, duration, and recording references transfer to custom Task fields. Meetings map to Event with StartDateTime, EndDateTime, and Location preserved. We set WhoId on Task and Event to the migrated Contact or Lead and WhatId to the related Opportunity or Account. Activity ordering is preserved by setting ActivityDate to the original Teamleader timestamp.

Teamleader custom field definitions are scoped per context: contact, company, deal, project, milestone, product, invoice, subscription, ticket. A field named 'Region' may exist on both Contacts and Deals but with different IDs and option sets. We enumerate all custom fields via Teamleader's customFieldDefinitions.list endpoint for each context during scoping, then create matching custom fields on the corresponding Dynamics 365 entity before record import begins.