Migrate from TeamSystem CRM to Salesforce Sales Cloud

TeamSystem Contacts with a linked Company record map to Salesforce Contact tied to an Account. TeamSystem Contacts without a linked Company (or where the Company is a personal account) map to Salesforce Lead for records where the customer wants to maintain an unqualified prospect queue. We query the contact_company_link field during extraction to determine AccountId resolution. The original TeamSystem contact identifier is preserved in an external ID field for downstream reconciliation.

TeamSystem Company records map directly to Salesforce Account. The Company name becomes Account.Name, and any registered business address fields map to BillingAddress. We extract the Company identifier separately for Contact lookup resolution during the import phase. Accounts are created before any Contact import so that the AccountId foreign key is satisfied at the moment of Contact insert.

TeamSystem Opportunity records map to Salesforce Opportunity with deal value, stage, expected close date, and pipeline association preserved. The TeamSystem dealstage and pipelineid fields map to Salesforce StageName and a pre-configured Record Type respectively. We query the stage ordering during discovery and replicate it as a Salesforce Sales Process with matching stage names and probability percentages.

Each TeamSystem pipeline definition becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Custom stage probabilities migrate from TeamSystem to StageProbability on each Salesforce OpportunityStage. We configure Record Types before migration begins so that Opportunities land in the correct pipeline context on insert.

TeamSystem call logs map to Salesforce Task with TaskSubtype set to Call. Call duration, disposition, and any associated notes transfer to custom Task fields. Activity timestamps preserve so the timeline ordering is maintained in Salesforce. We resolve the WhoId (Contact or Lead) and WhatId (Opportunity or Account) by matching against the migrated record IDs before insert.

TeamSystem meeting logs map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee information becomes EventRelation records linked to the relevant Contact, Lead, or User. We handle multiple attendees per meeting by creating a separate EventRelation for each participant referenced in the TeamSystem record.

TeamSystem email engagements migrate to Salesforce EmailMessage records (the content) linked to an Activity Task record (the timeline entry). The EmailMessage is linked to the Contact or Lead via the ParentId field, and the Task provides the standard activity timeline view. Email content and headers transfer as plain text; HTML body is stripped to Salesforce's supported format.

TeamSystem task engagements map to Salesforce Task with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving the TeamSystem owner reference to Salesforce OwnerId via the User mapping table. Completed versus open status carries forward so that the pipeline activity summary is accurate immediately after cutover.

Organization-specific fields on any standard TeamSystem object are extracted by querying the field registry before export to ensure all non-standard columns are included. Each custom field maps to a Salesforce custom field of equivalent type (text, number, date, picklist) with the API name suffixed __c. We pre-create the destination schema in a Salesforce Sandbox before any data import so that field dependencies are satisfied at insert time.

Files linked to deals, contacts, or activities export as ContentVersion records that become ContentDocument records in Salesforce. We download files by reference URL or via direct database fetch if API access is restricted, then re-upload through Salesforce's API. File size limits (250 MB per ContentVersion in most orgs) apply, and attachments exceeding this threshold are flagged during scoping for a manual handoff approach.

TeamSystem Lead records (with status, source, and scoring fields) map directly to Salesforce Lead. Lead_Status maps to Salesforce LeadStatus picklist values. Any custom scoring fields on the TeamSystem Lead become custom fields on the Salesforce Lead. We use the Lead as a holding queue for unqualified prospects and do not auto-convert them to Contact and Account during migration; the customer's admin handles the conversion workflow post-migration.

TeamSystem User records with role assignments and record ownership are mapped to Salesforce User records by email match. User IDs in TeamSystem do not map directly to Salesforce usernames, so we build a user mapping table during scoping and apply ownership reassignment during migration. Any TeamSystem Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import proceeds.

Email tracking and inbox association data from TeamSystem's integration layer migrates as Salesforce EmailMessage records linked to the parent Contact or Lead. Full email content may require separate export depending on the integration configuration and whether TeamSystem stores content in the CRM layer or the ERP layer; we confirm storage location during the data separation phase.

Automated workflow configurations stored in TeamSystem's ERP-CRM integration layer are not exportable as discrete data. We document every active workflow trigger, conditions, and actions during the discovery phase and deliver a written Workflow Inventory Report that maps each TeamSystem automation to a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds these post-migration; this is outside the standard migration scope.