Migrate from Teleforce CRM to Salesforce Sales Cloud

Teleforce Contacts map directly to Salesforce Contacts. The source schema is enumerated during discovery from customer-supplied field inventories since no API documentation exists. Standard fields (Name, Email, Phone, Title) map to their Salesforce equivalents. We preserve a teleforce_id__c external ID field for cross-reference and deduplication. Owner assignment migrates via email lookup against the destination User table with unresolved owners held in a reconciliation queue.

Teleforce Company records map to Salesforce Account. Company name becomes the Account Name; website becomes Website; industry and employee count map to typed fields. The Account is inserted before Contact import so that AccountId can be resolved at Contact insert time. We apply a name-dedupe key during import to prevent duplicate Accounts from repeated CSV runs.

Teleforce Deals map to Salesforce Opportunity with stage and pipeline context preserved. The source dealstage property maps to a Salesforce StageName value that we configure as part of the destination Sales Process. Closed-Won and Closed-Lost amounts and dates migrate to Amount, CloseDate, StageName, and IsClosed. OwnerId resolves via the User email lookup. If multiple pipelines exist, we assign RecordTypeId per pipeline at migration time.

Each Teleforce pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages transfer to StageProbability. Pipeline ordering and stage names come from explicit customer confirmation since no public schema documents Teleforce's default pipeline configuration.

Teleforce Activities (call logs, meeting records, task entries) migrate to Salesforce Task and Event. We use the Bulk API 2.0 for activity batches because Teleforce's activity volume is unknown until CSV extraction and Salesforce's standard Data Loader times out on large activity sets. WhoId (Contact or Lead lookup) and WhatId (Opportunity, Account, or Case lookup) resolve at migration time from the parent-record lookup table we build during the account-phase migration.

Teleforce Lead records (if present as a distinct lifecycle stage or object) map to Salesforce Lead. Lead Status maps from Teleforce's lead stage. Any lead scoring value in Teleforce migrates to a custom field lead_score__c. The customer confirms during discovery whether Leads and Contacts are separate objects or a single unified record type in their Teleforce configuration.

Teleforce Users referenced on Deals, Contacts, and Companies map to Salesforce Users by email match. We build an owner mapping table from the Teleforce CSV export and cross-reference against the destination org's User table before record migration begins. Any Teleforce Owner without a matching Salesforce User is flagged in a reconciliation report for the customer's admin to provision before import resumes.

Teleforce custom fields on Contact, Deal, and Company require explicit customer-supplied schema definitions because no public API or documentation lists them. We request a complete field inventory from the customer before designing the Salesforce schema. Custom fields map to typed Salesforce fields (Text, Number, Date, Picklist, Checkbox) based on data values observed in the CSV export. Custom fields are created in Salesforce before any data import.

Teleforce's unified inbox aggregates calls, SMS, emails, and chat into threaded views. Independent export of SMS and chat threads is not confirmed. Call log data migrates as Task records with TaskSubtype = Call and CallDurationInSeconds preserved where available in CSV. SMS and chat history is flagged as potentially incomplete and documented as a known gap in the migration scope.

Teleforce automations, AI bot flows, and follow-up sequences are not migratable. We document every active automation rule identified during discovery — including trigger conditions, actions, and delay configurations — in a written rebuild guide that maps each rule to a Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds automations post-migration. This is not included in the data migration scope.

Inline file attachments in Teleforce require direct database or UI export access. We migrate file URL references as Salesforce ContentDocumentLink records pointing to the original storage location, with the customer responsible for re-uploading files to Salesforce Files or a connected document management system. Blob-level attachment migration is not supported for Teleforce.

Teleforce tag support is not confirmed in available research. Where tags appear in CSV exports, we map them to a Salesforce custom Text field (comma-separated) or Topics with TopicAssignment records, depending on the customer's preference during scoping. Tag strategy is a configuration choice made with the customer before import.