Migrate from m-savvy to Salesforce Sales Cloud

M-savvy Contact records map directly to Salesforce Contact. Standard fields (Name, Email, Phone, Address) map to their Salesforce equivalents. Lifecycle stage, owner assignment, and any custom contact properties migrate to Salesforce custom fields prefixed with ms_ (e.g., ms_lifecycle_stage__c) to preserve provenance. Contact is inserted after Account so that AccountId lookup is satisfied at the moment of Contact insert.

M-savvy Account records map directly to Salesforce Account. The account name becomes Account Name, industry and size fields map to Industry and NumberOfEmployees, and billing address maps to BillingAddress fields. Account is created first because Contact records require an AccountId lookup.

M-savvy Deals map to Salesforce Opportunity. Deal stage maps to Salesforce StageName, deal amount maps to Amount, close date maps to CloseDate, and probability migrates to a custom field ms_probability__c since Salesforce calculates probability from the stage definition. Owner assignment maps via email match to Salesforce User records in the owner reconciliation step.

M-savvy Lead records map directly to Salesforce Lead. Lead status maps to LeadStatus, lead source maps to LeadSource, and any lead scoring properties migrate to custom fields. We check whether the destination org separates Leads from Contacts (the standard Salesforce model) and flag any m-savvy Contacts that may need to be treated as Leads in Salesforce versus Contacts if the customer has a flat data model.

M-savvy pipeline definitions are read from the live API during schema discovery. Each m-savvy pipeline maps to a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the stage values. Stage order and probability rounding follow Salesforce's allowed integer format. If m-savvy uses a single pipeline, we create one Record Type; multiple pipelines map to multiple Record Types.

M-savvy stage names map to Salesforce StageName picklist values within the mapped Sales Process. Stage probability percentages from m-savvy migrate to Salesforce StageProbability with rounding to the nearest integer. If a m-savvy stage has no Salesforce equivalent, we add it to the opportunity stage picklist during schema setup.

M-savvy Activity records are enumerated by type: call engagements map to Task with TaskSubtype=Call, email engagements map to Salesforce EmailMessage linked to a Task, meeting engagements map to Event, and standalone tasks map to Task. Activity timestamp preserves chronology by setting ActivityDate to the original m-savvy timestamp. Parent record resolution (WhoId, WhatId) uses the email-to-Contact lookup and deal-to-Opportunity lookup built during the mapping phase.

M-savvy custom object schemas are discovered via live API inspection because no public schema reference exists. We enumerate every custom object type, its fields, and its field types, then pre-create the Salesforce custom object and custom fields (with __c suffix) before any data import. Lookup relationships between custom objects and standard objects (Contact, Account, Opportunity) are resolved at migration time using the external ID we assign during schema setup. If a m-savvy plan tier restricts access to a custom object, we flag it in the discovery report and advise on upgrading before migration.

M-savvy attachments are stored separately from record data and require a dedicated file-export pass. We download each file via the m-savvy file API, store it in our staging environment, then upload to Salesforce as ContentVersion (the file body) with the associated ContentDocument linked via ContentDocumentLink to the parent record ID. If the parent record fails to migrate, its attachments are held in a manual review queue and reported separately.

M-savvy Owner records map to Salesforce User by email match. Any m-savvy Owner without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import proceeds. OwnerId references are required on most standard objects, so this step gates the record migration phases.

M-savvy team member records that are not assigned as Owners on records but exist as User entities map to Salesforce User. We extract all distinct User IDs from the m-savvy export and match against the Salesforce User table by email. Active and inactive status is preserved unless the customer specifies otherwise during scoping.

M-savvy notes linked to Contact, Account, Deal, or Lead records migrate to Salesforce Note objects. Note body preserves rich text formatting where m-savvy supports it. Notes are linked to the parent record via ContentDocumentLink after the ContentDocument is created during the attachment pass.