Migrate from Teamleader to monday CRM

Teamleader Contacts map to Person entities in a Monday.com CRM People board. The first_name and last_name fields from Teamleader compose the Person entity's display name; email addresses map to the email column. We resolve the Teamleader contact-to-company association and link the Person item to the corresponding Company entity in Monday.com using the Linked Items column. Any Teamleader contact custom fields scoped to the 'contact' context are mapped to equivalent Monday.com column types (text, number, date, dropdown) on the People board.

Teamleader Company records map to Company entities in Monday.com CRM's Companies board. The company_name field becomes the Company entity name; website maps to a URL column; address and VAT number map to text columns. We create Company entities before Person entities so that the person-to-company link is satisfied at import time. Teamleader's many-to-many contact-to-company relationship is resolved by linking each Person item to the relevant Company item via the Companies column on the People board.

Teamleader Deals map to items on a Monday.com CRM board configured as the sales pipeline. Each Teamleader Pipeline becomes a Group on the CRM board. Teamleader Stages within each Pipeline map to Status column values per Group. Deal value (total_amount) maps to a Numbers column; expected_close_date maps to a Date column. We resolve the deal's linked Contact and Company at migration time using Monday.com's People and Companies column types and insert the item into the correct Group (Pipeline) before import.

Teamleader Pipelines map to Groups on the Monday.com CRM board. We create a Group per Pipeline, renaming each to match the source Pipeline name. Teamleader Stages within each Pipeline become Status column values assigned per Group, so that deals land in the correct stage workflow immediately on import. The StageProbability from Teamleader (if present) is stored in a Numbers column for reference rather than mapped to a native Monday.com probability field.

Teamleader Tickets map to items on a dedicated Monday.com support or CRM board. Ticket status maps to a Status column; priority maps to a Priority or Labels column; assignee maps to the Person column. We resolve the linked Company from Teamleader's ticket company association to a Monday.com Company entity via Linked Items. The ticket conversation thread migrates as a series of Updates attached to the item, preserving timestamps and author names, though native email threading requires reconnection of the email inbox integration post-migration.

Teamleader Projects map to boards in Monday.com Work Management (a separate product line from CRM boards). Each Project becomes a board with Groups representing Milestones. We note that Monday.com Work Management and Monday.com CRM are separate product lines with different permission models, so the customer may need separate board sharing configuration for teams that span sales and operations. Projects requiring CRM linkage (client-facing project boards linked to deal records) are configured as cross-board linked items referencing the CRM board.

Teamleader Milestones are sub-objects of Projects. In Monday.com Work Management boards, we represent Milestones as Groups within the Project board, with each Milestone's due date, budget, and status mapped to column values. For projects requiring subitem-level granularity, Milestones can alternatively be represented as subitems of a parent Project item. The choice is made during scoping based on the customer's existing Milestone usage patterns.

Teamleader Products (catalog items used in Quotations, Invoices, and Subscription line items) map to items on a Products board in Monday.com with columns for product_name, price, unit, and hs_sku (mapped from Teamleader's code field). The Products board is referenced by deal line items and invoice items via the Item column type. Customers requiring a native product catalog with pricing lists should evaluate Monday.com's product management capabilities against their specific quoting workflow needs during scoping.

Teamleader Invoice headers (invoice number, date, due date, line items, tax codes, payment status) migrate to items on a dedicated Invoices board in Monday.com as structured records. However, QR-code payment state, automatic payment reminder triggers, and overdue flag resets are tied to Teamleader's payment processing system and do not transfer. We flag each Invoice record as requiring payment reminder reconfiguration post-migration. Customers actively using Teamleader's invoicing for billing should plan to either use Monday.com's native invoicing (Standard plan and above) or maintain a separate accounting system post-migration.

Teamleader Subscriptions (recurring billing relationships with defined periodicity and pricing) migrate to items on a Subscriptions board in Monday.com. The subscription period, frequency, pricing, and linked Contact and Company map to typed columns. Auto-renewal triggers and subscription pause or cancel automation rules do not migrate because they are Teamleader-specific workflow events. We document each active Subscription with its periodicity and pricing for manual reconfiguration in Monday.com's automation center or a connected billing integration.

Teamleader Activities (Tasks, Meetings, Phone calls) with owner, due date, and linked Contact or Deal map to Updates on the relevant Monday.com CRM board item. The Update preserves the activity description, timestamp, and author name. For accounts with high activity volume, we can alternatively create a dedicated Activity board where each activity becomes an item linked to the Contact and Deal via People and Item columns, enabling filtering and reporting across the activity history. The customer chooses the approach during scoping based on their reporting needs.

Teamleader custom fields are scoped per context (contact, company, deal, project, milestone, product, invoice, subscription, ticket). During scoping we call the Teamleader customFieldDefinitions.list endpoint for each context in scope and map each to the closest Monday.com column type: text fields to Text columns, numeric fields to Number columns, date fields to Date columns, and option-set fields to Dropdown or Status columns. Monday.com custom field dependencies (where one field must be configured before another) are handled by ordering column creation to respect the dependency chain.