Migrate from Salesmate to Salesforce Sales Cloud

Salesmate Contacts (Module ID 1) map directly to Salesforce Contact. Standard fields (FirstName, LastName, Email, Phone, MailingAddress) migrate with direct type matching. Custom fields migrate to Salesforce custom fields with __c suffix. Lifecycle stage from Salesmate's Contact record maps to a custom field sm_original_lifecycle__c on the Contact for reporting continuity. HubSpot-style Contact-Company linking is preserved via AccountId lookup resolution after Account import completes.

Salesmate Companies (Module ID 5) map to Salesforce Account. Company name maps to Account Name; domain maps to Website. Companies are imported before Contacts so that the AccountId foreign key is resolved at Contact insert time. Multi-address Company records (billing vs shipping) map to Account BillingAddress and ShippingAddress. Custom fields on Company migrate to Account __c fields matching the source field types.

Salesmate Deals (Module ID 4) map to Salesforce Opportunity. Deal stage maps to Salesforce StageName via a pre-configured Sales Process that whitelists the source stage values. Deal value, close date, owner, and associated Contact and Company links migrate with OpportunityId, AccountId, and OwnerId resolved at migration time. Loss reason and win reason custom properties map to Salesforce LossReason and custom win-reason fields.

Each Salesmate pipeline with its stages becomes a Salesforce Record Type with a corresponding Sales Process. Stage probabilities migrate from Salesmate to StageProbability values rounded to Salesforce-allowed integers. If the customer uses multiple Salesmate pipelines, each maps to a separate Record Type with stage values scoped to that line of business.

Salesmate Products (Module ID 6) map to Salesforce Product2. Product pricing, description, and SKU migrate to ProductCode and Description. Standard Pricebook entries are created during import with the destination org's default Pricebook2 referenced. Currency handling defers to the org's multi-currency settings if active.

Salesmate Tasks (Module ID 2) map to Salesforce Task with Status, Priority, ActivityDate, and Subject preserved. Owner resolution matches Salesmate owner email to Salesforce User email. Task associations to Contact or Deal migrate as WhoId and WhatId on the Salesforce Task record. Open/closed status maps directly to Salesforce Task Status values.

Salesmate email history (Module ID 3) migrates to Salesforce as paired Task (activity timeline entry) and EmailMessage (email body content) records. Task WhoId points to the Contact; WhatId points to the related Opportunity or Account. Thread metadata from Salesmate preserves as custom fields if the destination org has no native thread-equivalent. Email attachments migrate as ContentDocumentLink records attached to the EmailMessage.

Salesmate call recordings and SMS logs require separate endpoint handling beyond the standard REST API. We extract call disposition, duration, direction, and recording URL from the call-log endpoint and map them to Salesforce Task custom fields (TaskSubtype = Call, CallDisposition, CallDurationInSeconds, CallType). Recording audio files migrate as ContentDocument records linked via ContentDocumentLink to the parent Contact or Opportunity. SMS logs migrate as Task with a custom subtype and the message body in a custom long-text field.

Salesmate Team Inbox shared conversations with threading metadata do not map natively to any Salesforce standard object. We extract thread membership, response timestamps, and team-member attribution per message and preserve them as custom fields on EmailMessage (sm_thread_id__c, sm_team_inbox__c, sm_responder__c). The shared inbox identifier maps to a Salesforce Group or a dedicated Queue. Email body content migrates as EmailMessage records linked to the appropriate Contact, Account, or Opportunity. This mapping is documented in the handoff inventory for the customer's admin to evaluate whether Salesforce Inbox or a shared Salesforce Email-to-Case setup is the appropriate long-term replacement.

Salesmate tags on Contacts and Companies export as string arrays via the API. Tags migrate to Salesforce multi-select picklist fields on Contact and Account. The customer chooses between native multi-select picklist (immediate filtering in list views) or Salesforce Topics (with TopicAssignment records for broader taxonomy use) during scoping.

Salesmate Users map to Salesforce Users by email address match. We request a full-access admin Access Key from Salesmate during scoping to ensure all user records and permission data are retrievable. Any Salesmate Owner referenced on a record without a matching Salesforce User is held in a reconciliation queue; the customer's admin provisions the missing User before record import resumes.

File attachments associated with Contacts, Deals, and Companies are migratable via the Salesmate API. Files migrate as Salesforce ContentVersion (file body) with ContentDocumentLink records linking to the parent Contact, Account, or Opportunity. Salesmate file storage limits (1 GB Basic, 5 GB Pro, 10 GB Business, 20 GB Enterprise) do not constrain Salesforce file storage, which uses org-wide data storage limits.