Migrate from Simplero to Salesforce Sales Cloud

Simplero Contacts with Lifecycle Stage of prospect or subscriber map to Salesforce Lead. Lifecycle Stage of customer or active member maps to Salesforce Contact tied to an Account. We compute the split using Simplero's contact lifecycle property during the transform phase, preserving the original Simplero lifecycle stage in a custom field simplero_lifecycle__c on both Lead and Contact for reporting continuity. Any Tags applied to the Contact migrate as multi-select picklist values on the target record.

Simplero Company records (if present from a legacy CRM import into Simplero) map to Salesforce Account. The domain or website field from Simplero becomes the Account Website field and is used as a dedupe key during import. Account is created before Contact import so that AccountId lookup is satisfied at the moment of Contact insert.

Simplero Tags are flat key-value labels stored against each Contact. We migrate them as Salesforce multi-select picklist fields on the Contact or Lead object. For migrations with more than 200 distinct tag values, we recommend creating a Topic-based taxonomy using Salesforce Topics and TopicAssignment records instead of proliferating picklist values.

Simplero Segments are dynamic filter groups that define audience segments. We export the contact-to-segment membership as explicit membership records and map each Simplero Segment to a Salesforce Campaign with MemberStatus preserved. Static segments migrate as Campaign Members; dynamic segments are documented as filter criteria for the customer to recreate as Salesforce Reports or Campaign membership rules.

Simplero Deals (Skyrocket tier only) map to Salesforce Opportunity. Deal stage, value, owner, and close date transfer directly. The Simplero deal pipeline maps to a Salesforce Record Type and Sales Process that we configure before migration. We apply stage probability percentages to match Simplero's stage weighting if those were configured.

Simplero Products (courses, memberships, coaching programs, digital downloads) map to Salesforce Product2 records with Standard Price Book entries. Product type classification (course vs membership vs 1:1 session) migrates as a custom field product_type__c on Product2. Pricing and access rules are preserved in the Product2 description and custom fields for admin reference.

Simplero Members (contacts with active product access) and Enrollment records (which contact has access to which product and when) require a custom Enrollment__c junction object in Salesforce with lookups to Contact and Product2. We design the junction schema during scoping, deploy it to Sandbox for validation, then migrate enrollment history as historical records. Without a custom object, enrollment data collapses into note fields and becomes unreportable.

Simplero Order records (product, price, date, payment gateway, refund status) map to Salesforce Opportunity records with custom order fields (simplero_order_id__c, payment_gateway__c, refund_status__c). Refund flags and partial payment states migrate as custom Opportunity fields with value mappings applied during transform. If the customer uses Salesforce Orders (available from Professional), we use the standard Order object instead.

Simplero email broadcast history migrates to Salesforce EmailMessage records linked to an Activity Task. The email subject, body, and send timestamp transfer. Salesforce EmailMessage requires the HasBlogEmailHeader__c custom flag to be set for bulk loads to bypass certain validation. We use Bulk API 2.0 for large broadcast histories with exponential backoff.

Simplero Email Sequences (multi-step automation content) are migrated as a custom Sequence__c object containing step records with send order, delay, and content. We do not migrate sequence logic (triggers, delays, conditions) as code because Simplero does not expose it via API. The customer receives a written sequence map with trigger conditions and step content for rebuild in Salesforce Sales Engagement or Flow.

Simplero call records map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and recording URL (if available via API) migrate as custom Task fields. Activity timeline ordering is preserved by setting ActivityDate to the original Simplero timestamp.

Simplero meeting records map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee records migrate as EventRelation records linking to the relevant Contact, Lead, or User.

Simplero Notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Lead, Account, or Opportunity. Rich text formatting and any embedded image attachments migrate as separate ContentDocument records.

Simplero help desk tickets (Scale+ only) migrate to Salesforce Case. Ticket pipeline maps to Case Record Type, ticket status maps to Case Status, and conversation threads migrate as EmailMessage records linked to the Case. We flag Simplero's chat and AI bot conversation history as out of scope because Simplero does not expose this via API.

Simplero Site Pages are migrated as structured content records (Title, Body, Slug, Meta Description) with slug paths preserved in a custom field for URL redirect planning. We do not migrate the site builder theme, CSS, or media assets. The customer receives a slug map document to wire up 301 redirects in Salesforce Experience Cloud or their hosting provider.

Simplero blog posts export via RSS XML format and migrate as Salesforce Content records or custom Knowledge Article records. Post slugs are preserved for redirect mapping. Author attribution, publish date, and category tags transfer as custom fields.

Simplero community posts and comment threads migrate as Salesforce Chatter FeedItem records or as a custom CommunityPost__c object depending on whether the destination org has Chatter enabled. Reactions and upvotes map variably to custom vote count fields. We flag Simplero private community posts as requiring explicit customer consent before migration.

Simplero Automation Flows are not accessible via API and cannot be migrated. We document every active Simplero Flow during discovery: trigger event, step sequence, conditions, and action chains. The customer receives a written Flow inventory with a recommended Salesforce Flow equivalent for each sequence. Rebuilding Flows in Salesforce is outside the standard migration scope.