Migrate from Teamleader to Nutshell

Teamleader Contact records map to Nutshell Contact with name, email, phone, address, and social fields preserved. Teamleader's separate contact custom fields (scoped via the 'contact' context on customFieldDefinitions.list) map to Nutshell custom fields on the Contact object. Because Nutshell combines Contact and Company into one object model, we check each Teamleader Contact for a linked Company and populate the Company name field on the Contact record if the link exists.

Teamleader Company records merge into Nutshell Contact records where the Company name becomes the Company field on the Contact object. The Teamleader Company address, VAT number, and custom fields (scoped via 'company' context) map to Nutshell Contact fields. We use Company name as the dedupe key during import to prevent duplicate Contact records. If a Teamleader Contact has no linked Company, we import it as a standalone Nutshell Contact without populating the Company field.

Teamleader Deals map to Nutshell Opportunity. The deal title becomes the Opportunity name; deal amount, close date, and stage migrate directly. Pipeline assignment from Teamleader maps to the Nutshell pipeline, and Teamleader deal stages map to Nutshell pipeline stages with stage probability percentages preserved. Owner resolution uses email matching against the Nutshell user list.

Teamleader pipelines (1 on SMART, 2 on GROW, unlimited on FLOW) map to Nutshell pipelines. We configure Nutshell pipeline stages to match the Teamleader stage names and probabilities. Teams with two Teamleader pipelines create two Nutshell pipelines or use Nutshell's list view with filtering if they are on Foundation (1 pipeline) or Growth (1 pipeline); Pro and above support multiple pipelines.

Teamleader Quotations migrate to Nutshell Quotes using Nutshell's native Quoting tool (available on Growth and above tiers). The quotation title, line items, pricing, expiry date, and margin data transfer. Nutshell Quotes are linked to the Contact (from the merged Company/Contact mapping) and Opportunity. Quotations on Teamleader SMART tier (which may have limited quotation features) migrate as Quotes on Nutshell Growth or Pro.

Teamleader Products map to Nutshell Products with name, SKU, description, pricing, and custom fields (scoped via 'product' context) preserved. ProductCode maps from Teamleader's product code. Products are created in Nutshell before Quote migration so that line item references are satisfied.

Teamleader Projects have no native equivalent in Nutshell. We create a Nutshell custom object (Project__c) with fields for project name, description, status, budget, and due date. Milestones map to sub-tasks on the Project__c custom object or to related Task records. Custom fields scoped under 'project' and 'milestone' contexts in Teamleader are recreated on the destination schema. Project-time-linked activities require the Project__c custom object to exist before Task migration.

Teamleader Milestones migrate as Nutshell Tasks linked to the Project__c custom object. Due date, budget status, and milestone name transfer. Custom fields on Milestones (scoped via 'milestone' context) become custom fields on the Task record. Milestone ordering is preserved by setting Task sequence or a custom milestone_order field.

Teamleader Invoices have no native equivalent in Nutshell. We create a custom object (Invoice__c) to preserve invoice headers, line items, tax codes, and payment status. Note that 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 so the customer can reactivate payment reminders or integrate a billing tool post-migration.

Teamleader Subscriptions (recurring billing relationships with periodicity and pricing) have no native Nutshell equivalent. We create a Subscription__c custom object with fields for subscriber name, periodicity, pricing, status, and linked Contact. Custom fields scoped via 'subscription' context are recreated on the destination schema.

Teamleader Tickets migrate to Nutshell Cases. Ticket status workflow, assignee, priority, and linked Contact or Company association transfer. Custom fields scoped via 'ticket' context map to custom fields on the Nutshell Case object. Ticket conversations migrate as Activity records or notes on the Case.

Teamleader Time Entries linked to Projects or Tasks migrate as Nutshell Tasks with duration, billable flag, and user assignment preserved. Time entries without a project link are imported as standalone tasks. The linked Project__c custom object must exist before time entry migration so that the parent reference is satisfied.

Teamleader activity types map to Nutshell Task and Event. Tasks with a due date become Nutshell Tasks with due date. Meetings become Nutshell Events with start and end time. Phone calls become Tasks with a call type marker. The linked Contact or Deal (Opportunity) reference resolves via the Contact and Opportunity mapping completed earlier in the migration sequence.

Teamleader custom field definitions are scoped per context (contact, company, deal, project, milestone, product, invoice, subscription, ticket). We enumerate custom fields via the Teamleader customFieldDefinitions.list API for each context, then pre-create equivalent custom fields in Nutshell with matching types (text, number, date, picklist, checkbox). Custom field values migrate as part of each object migration phase.