Migrate from Teamgate to Salesforce Sales Cloud

Teamgate People records map to Salesforce Lead or Contact depending on deal engagement. Records with at least one associated Deal or with a lead_status property set to qualified map to Salesforce Contact tied to an Account. All other People records map to Salesforce Lead. We compute the split using the Teamgate person's associated_deals array and custom property values at migration time, preserving the original Teamgate Person ID in a custom field teamgate_person_id__c for audit. This split is the most consequential design decision in a Teamgate migration and must be validated in Sandbox before production.

Teamgate Company records map directly to Salesforce Account. The company domain and industry classification fields migrate to Account Website and Industry. Account is created before any Contact or Lead import so that the AccountId lookup is satisfied at the moment of insert. We use Company name as the dedupe key to prevent duplicate Account creation when the same company appears across multiple People records.

Teamgate Deals map to Salesforce Opportunity. The pipeline assignment determines which Salesforce Record Type we apply; the dealstage property maps to StageName within the corresponding Sales Process. Deal value (amount), expected_close_date, and loss_reason migrate directly. We flag Deals with no associated Company for the customer to resolve before import because Salesforce requires an AccountId or Account.Name on Opportunity.

Each Teamgate Pipeline becomes a Salesforce Record Type on Opportunity. The Record Type gets its own Sales Process that whitelists only the relevant stage values, preserving the stage sequence and probability weights from Teamgate. Probability percentages migrate to Salesforce StageProbability, rounded to the nearest integer as Salesforce requires. Teams with two Pipelines get two Record Types; teams with five get five.

Each Pipeline Stage in Teamgate maps to a Stage value within the Salesforce Sales Process assigned to that pipeline's Record Type. Stage order, stage name, and probability weight are preserved. If Teamgate has a Closed Lost stage with a custom loss reason dropdown, we map it to Opportunity.Loss_Reason__c (a custom field we create) and the standard StageName.

Teamgate custom field schema exports via API alongside each record. Field types (text, number, date, dropdown, checkbox) map to Salesforce equivalents: text to Text, number to Number, date to Date, dropdown to Picklist, checkbox to Checkbox. We pre-create all destination custom fields via the Salesforce metadata API before importing data, using the original Teamgate field label as the Salesforce field label with a __c suffix. Required field constraints are set to not required during import to avoid blocking records with sparse data.

Teamgate tags are flat string labels applied to People, Companies, and Deals. We export tags as normalized comma-separated lists per record. At the destination, tags on People/Lead migrate to a Salesforce multi-select picklist field; tags on Deals/Opportunity migrate to a custom text field formatted as tag1;tag2;tag3. The customer chooses the tag strategy during scoping based on their tagging taxonomy.

Teamgate activity logs (type: call, email, meeting, task) attached to People or Deals migrate to Salesforce via the Bulk API. Calls become Task with TaskSubtype=Call and CallDisposition preserved in a custom field. Emails become Salesforce EmailMessage records linked to Tasks. Meetings become Event with StartDateTime and EndDateTime preserved. Standard tasks become Task records. The WhoId (Contact or Lead) and WhatId (Opportunity or Account) are resolved at migration time using the Teamgate activity's associated_person_id and associated_deal_id cross-references.

Loss reasons are a configurable dropdown in Teamgate tied to Deals. We export all active loss reason values as a custom picklist field Loss_Reason__c on Opportunity, creating new picklist values during schema creation. If the destination Salesforce org already has a loss reason field, we map to it instead. Loss reasons on Deals with no Deal must be handled separately; we flag these for the customer admin to review.

Teamgate Owner records (the rep assigned to a Deal, Company, or Person) export with name, email, role, and active status. We match Owners by email against the Salesforce destination org's User table during scoping. Any Owner without a matching Salesforce User goes to a reconciliation queue; the customer's admin provisions the missing User before record import resumes. Inactive Teamgate owners map to inactive Salesforce Users with a note in the reconciliation report.

Teamgate file metadata (name, URL, storage location) exports via API, but actual binary files must be downloaded from Teamgate and re-uploaded to Salesforce as ContentDocument records. We provide a file inventory spreadsheet listing every file, its parent record (Person, Company, or Deal), and its Teamgate download URL. The customer's admin downloads files and uploads them to Salesforce via Data Loader or the UI, linking them to the migrated parent record using the ContentDocumentLink table. This step is manual because Teamgate's API does not expose binary download tokens for programmatic extraction.

OAuth tokens for Gmail and Outlook, Twilio SmartDialer credentials, Zapier webhook configurations, QuickBooks connections, and Xero links are not exportable via Teamgate's API and cannot be migrated. We deliver a written integration inventory listing every active integration, its configuration parameters, and the equivalent Salesforce or AppExchange replacement. The customer configures new integrations post-migration. SmartDialer service in Teamgate must be canceled or downgraded separately to stop usage-based billing charges.