Migrate from TeamWave to Salesforce Sales Cloud

TeamWave Contacts with lifecycle_stage of subscriber, lead, or marketing-qualified lead map to Salesforce Lead. Lifecycle stage of customer, evangelist, or other post-sale stages map to Salesforce Contact tied to an Account. We compute the split at migration time using the lifecycle_stage and contact_status properties and preserve the original TeamWave lifecycle stage in a custom field tw_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

TeamWave Company records map directly to Salesforce Account. The Company name becomes Account Name; the domain field (if present) becomes Website. The company_id foreign key is retained as tw_company_id__c for reconciliation. Account is inserted before any Contact import so that the AccountId lookup is satisfied at Contact insert time. Companies without a name are flagged for the customer's admin to review before the Account batch is finalized.

TeamWave Deals map to Salesforce Opportunity. The dealstage property maps to Salesforce StageName; the linked pipeline object maps to a Salesforce Record Type and Sales Process configured before migration. Deal value, expected close date, owner, and notes migrate directly. Closed-won and closed-lost reasons from TeamWave custom properties map to Salesforce Loss Reason and custom Win Reason fields.

Each TeamWave deal pipeline stage becomes a Salesforce StageName entry in a Sales Process. Stage probability percentages migrate from TeamWave to Salesforce StageProbability, rounded to the nearest integer. The TeamWave pipeline-column order is preserved in the Sales Process stage order.

TeamWave Projects map to a Salesforce custom object named Project__c (API name Project__c) created during schema design. Project fields (name, description, status, start date, end date, client association) migrate as Project__c fields. The client_id foreign key resolves to the Salesforce AccountId. If the customer prefers not to create a custom object, Projects migrate as Tasks with WhatId pointing to the related Account and a project_name__c custom field.

TeamWave Tasks map to Salesforce Task. Assignee resolves via email match to Salesforce User. Due date, priority, status, and description migrate directly. Task records linked to Projects preserve the project_id foreign key as project_id__c for reconciliation against the Project__c custom object mapping. Task records without a resolved Owner are placed in a hold queue for admin provisioning.

TeamWave User records (name, email, role, department) map to Salesforce User. We match by email address. Any TeamWave user referenced as an owner on Deals or Tasks without a matching Salesforce User goes to a reconciliation queue for admin provisioning before migration resumes. Department and role from TeamWave map to Salesforce Department and Title fields.

TeamWave calendar events map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Linked entity (Deal, Project, or Contact) maps to WhatId or WhoId on Event. Attendees resolve to EventRelation records pointing at the matched Users, Leads, or Contacts.

TeamWave Employee records map to Salesforce Employee__c (a custom object) or to Contact records with an IsEmployee__c checkbox flag, depending on the customer's Salesforce edition and org strategy. Name, role, department, and employment status migrate as custom fields. This object is optional; we confirm the preferred strategy during scoping.

TeamWave custom fields on Contacts, Deals, Projects, and Tasks export with their field definitions. We create equivalent custom fields in Salesforce during schema design, type-mapping to the closest Salesforce field type (text, number, date, picklist, checkbox). Fields without a direct Salesforce equivalent are flagged for the customer's admin to review and resolve.

TeamWave provides no bulk attachment download mechanism. We extract attachment metadata (filename, file size, linked object type, linked object ID) and produce a re-upload manifest for the customer's admin. No binary files are migrated. The manifest includes the destination object ID for each attachment so that manual re-upload targets the correct record.

TeamWave contact and deal tags stored as multi-value properties migrate to Salesforce multi-select picklist fields on the corresponding object. We flatten the tag list during transformation so each tag appears as a picklist value. The customer confirms the tag strategy during scoping.