Migrate from Simplicity Enterprise CRM to Salesforce Sales Cloud

Simplicity Contact records with a lifecycle or status property indicating a qualified prospect map to Salesforce Contact tied to an Account. Contacts representing marketing prospects or unconverted leads map to Salesforce Lead. We extract the status and segment membership from Simplicity to determine the split, and we preserve the original Simplicity contact ID in a custom field simplicity_contact_id__c on both Lead and Contact for audit and future reference.

Simplicity Company records map directly to Salesforce Account. Company name and address fields migrate 1:1. The Account is created before Contact import so that the AccountId lookup relationship is satisfied at the moment of Contact insert. We use Company name and domain as the dedupe key during import.

Simplicity Deal records map to Salesforce Opportunity. Deal stage names from Simplicity map to Salesforce StageName values that we pre-configure as part of the Sales Process setup. Deal value, close date, and custom deal fields migrate to Opportunity.amount, Opportunity.closeDate, and custom Opportunity fields respectively.

Simplicity's configurable pipeline stages map to a Salesforce Sales Process with stage values, probabilities, and forecast category configured to match the customer's deal workflow. We extract the full stage list during schema discovery and deploy it as a Salesforce metadata Sales Process before any Opportunity records load.

Simplicity Activities linked to Contact and Company records migrate to Salesforce Task and Event. We traverse the linked activity table explicitly because a naive Contact export does not include activity history. Emails land as Salesforce EmailMessage records; calls land as Task with TaskSubtype=Call; meetings land as Event; standalone notes land as Salesforce Note. WhoId and WhatId on each record are resolved to the migrated Lead, Contact, Account, or Opportunity ID at import time.

Simplicity Campaign records map to Salesforce Campaign. Campaign name, type, status, start date, and end date migrate directly. Campaign budget and expected revenue migrate to Campaign.BudgetedCost and Campaign.ExpectedRevenue if populated in Simplicity.

Simplicity campaign response tracking stores which Contact responded to which Campaign through which channel. Salesforce does not have a direct campaign-response object; we map these to CampaignMember records with Status reflecting response (Responded, Sent, No Response) and the channel stored in a custom CampaignMember field simplicity_channel__c. This preserves the behavioural signal without disrupting Salesforce's standard campaign model.

Simplicity segments define which Contacts belong to which behavioural or demographic groups. We offer two approaches: map segments to Salesforce Campaigns (one Campaign per segment) with affected Contacts as CampaignMembers, or create a custom Simplicity_Segment__c object with a junction object Simplicity_Segment_Member__c linking Contacts to their segment memberships. The customer chooses during scoping based on how segments are used in downstream reporting.

Simplicity Loyalty stores program rules, reward tiers, point balances, and membership records as separate relational records linked to Contact. Salesforce has no native loyalty object. We create a Simplicity_Loyalty_Program__c custom object for program-level data, a Simplicity_Loyalty_Tier__c object for tier definitions, and a Simplicity_Loyalty_Member__c junction object for the contact-to-program relationship with point_balance and membership_date fields.

Simplicity stores social follower counts and interaction records integrated with the contact profile. Salesforce has no standard social data object. We archive social metadata as a Salesforce Note attached to the Contact record, or we create custom fields (simplicity_social_followers__c, simplicity_social_interactions__c) if the customer requires the data visible on the contact layout without a separate note.

Simplicity's configurable schema means nearly every object can carry client-defined custom fields. We enumerate every active custom field during schema discovery, map each to a Salesforce custom field of equivalent type (text, number, date, picklist, checkbox, formula), and deploy the schema to the destination org before any data loads. Client-specific picklist values from Simplicity migrate as Salesforce picklist restricted values or as a controlled set on the target field.

File attachments linked to Contacts, Companies, or Deals in Simplicity migrate as Salesforce ContentDocument records linked via ContentDocumentLink to the parent record. We extract attachments separately from the record export, map the file content and original filename, and attach each to the corresponding migrated record in Salesforce.