Migrate from Teamwork CRM to Salesforce Sales Cloud

Teamwork CRM Company records map directly to Salesforce Account. Company is the first object we extract and the first we load because every Contact in Salesforce requires an AccountId lookup. The Company name becomes Account Name, domain fields map to Website, and any billing or firmographic custom fields map to custom Account fields. We apply a dedupe key on Account Name plus Website domain during staging to catch duplicates before insert.

Teamwork CRM Contact records map to Salesforce Contact. Each Contact requires an AccountId reference at insert time, which we resolve by matching Contact.CompanyId to the migrated Account.id in the staging layer. Standard fields (name, email, phone, address) map 1:1; custom Contact fields map by name with type verification — Teamwork text custom fields map to Salesforce Text, Teamwork integer fields to Number, and Teamwork dropdown fields to Picklist. Contacts without a valid AccountId go to a reconciliation queue.

Teamwork CRM Lead records map to Salesforce Lead if the customer uses Teamwork's optional Leads pipeline alongside the Opportunities pipeline. Lead status, source, and any custom fields migrate directly. We do not convert Leads to Contacts during migration — that action is left for the customer's sales team post-migration so that the right owner drives the conversion in the correct Salesforce context.

Teamwork CRM Opportunity records map to Salesforce Opportunity. Deal value maps to Amount, close date maps to CloseDate, probability maps to Probability, and stage name maps to StageName after we configure the Salesforce Sales Process to match Teamwork's stage labels. OwnerId resolves via email match against the Salesforce User table. Opportunities without an AccountId go to a reconciliation queue.

Each Teamwork CRM pipeline (Leads pipeline and Opportunities pipeline if both are active) becomes a Salesforce Record Type on the Opportunity or Lead object. The Sales Process is configured to whitelist only the stage values that belong to that pipeline. Stage probability percentages transfer from Teamwork to Salesforce StageProbability, rounded to the nearest integer Salesforce accepts.

Teamwork CRM stage names, sort order, and custom probability weights map to Salesforce Opportunity Stage values within the configured Sales Process. Stage labels are preserved as StageName values; deprecated stages the customer has retired are flagged for the admin to archive post-migration. Any auto-prioritization rules in Teamwork are documented as a reference for Salesforce sorting logic the admin configures.

Teamwork CRM activity records (calls, meetings, and tasks linked to Contacts or Opportunities) map to Salesforce Task and Event. Calls map to Task with TaskSubtype=Call; meetings map to Event with StartDateTime and EndDateTime preserved; standalone tasks map to Task with Status and ActivityDate preserved. The WhoId on Task resolves to the migrated Contact or Lead id; the WhatId resolves to the migrated Opportunity or Account id. Activity records without a resolvable parent record are attached to the Account as a fallback.

Teamwork CRM custom fields support three types only — short text, integer number, and dropdown. We map these to Salesforce custom fields of equivalent type: Teamwork text becomes Salesforce Text, Teamwork integer becomes Salesforce Number, and Teamwork dropdown becomes Salesforce Picklist. Multi-select, date, and boolean custom fields do not exist in Teamwork CRM so this mapping gap does not apply here. Custom fields are created in Salesforce via metadata API before any record migration begins.

Teamwork CRM Users (the sales team members who own records) are mapped to Salesforce Users by email address. We extract every distinct owner_id referenced across Contacts, Companies, Opportunities, and Activities. Any owner without a matching Salesforce User email goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active vs inactive status mirrors Teamwork.

Teamwork CRM tags on Contacts and Opportunities are loose-label segmentation markers with no hierarchical structure. If the tag count is under 100 unique values, we map tags to a Salesforce multi-select picklist on the target object. If the tag count exceeds 100, we map to a custom text field and note that the customer should evaluate Salesforce Topics or a dedicated segmentation tool. The customer chooses the strategy during scoping.

Teamwork CRM does not support attaching files or email threads to Contact records. This is a documented platform limitation cited across G2 and Capterra reviews. We do not migrate file attachments associated with Contacts because the source object does not support them. If the customer has attached files stored in a separate system (Google Drive, SharePoint, Dropbox) linked to Teamwork records via URL custom fields, those URL references can be preserved in a custom text field in Salesforce.

Teamwork CRM saved custom filters are workspace-level configurations that do not carry business data. We capture filter definitions (field conditions, operator logic, sort order) as a JSON reference document delivered alongside the migration. Salesforce admins use this document to recreate equivalent list views and report filters in Salesforce Lightning.