Migrate from Splio to Salesforce Sales Cloud

Splio Contact records map to Salesforce Contact. The critical migration step is the list-membership audit before export: Splio silently excludes any contact not assigned to at least one list. We flag orphan contacts, assign them to a catch-all list or segment, verify the post-export count matches the full contact total, and then import all contacts into Salesforce. Email address is the dedupe key. Custom fields scoped to contacts migrate as Salesforce custom fields on Contact with equivalent data types.

Splio Order records map to Salesforce Opportunity. Each order links to a contact (the buyer) and carries order_items referencing products. The Splio order_id is preserved as Opportunity.Splio_Order_ID__c and becomes the dedupe key for the import. If an order with the same order_id is re-imported, Splio replaces the existing record; we use Upsert semantics in Salesforce with the Splio Order ID as the external key to replicate this behavior.

Splio order_items (individual line items) map to Salesforce OpportunityLineItem. Splio requires the parent order to exist before order_items can be imported; we enforce the same dependency in Salesforce by importing Opportunities first, then resolving the OpportunityId and PricebookEntryId before inserting line items. Quantity, unit price, and product reference map directly.

Splio Products are standalone items referenced by order_items. Product attributes and custom fields (products scope) map to Salesforce Product2 and PricebookEntry. ProductCode from Splio maps to ProductCode. We create Standard Price Book entries during import so that OpportunityLineItems can reference them.

Splio Loyalty memberships carry card_code, q_points (quantized points), nq_points (non-quantized points), and tier. These have no Salesforce standard equivalent, so we create a Loyalty_Membership__c custom object with those fields plus a lookup to Contact. Point balances migrate as numeric fields. Fractional values are preserved if present in Splio. Tier name migrates as a text or picklist field depending on program complexity. Membership creation date and last activity date migrate as custom date fields.

Splio Rewards are defined at the program level; attributions track which contacts received which rewards. Both interact with the Loyalty scope. We create a Reward__c custom object with reward name, type, value, and attribution fields, linked to Loyalty_Membership__c via lookup. Attributions migrate as Reward_Attribution__c records or as a junction object depending on whether Splio tracks multiple reward types per membership.

Splio Store records represent physical retail locations and e-commerce sites with location attributes. We map Store to Salesforce Account using Account Name as the primary field and Store ID as an external key. Location attributes (address, city, country) map to standard Account address fields. Custom fields scoped to stores migrate as custom fields on Account.

Splio Lists drive contact segmentation and export eligibility. We map list membership to Salesforce Campaign membership (CampaignMember records) with Campaign as the segment container. List names become Campaign names. Blocklists migrate as suppression campaigns or a custom Suppression_List__c field on Contact to ensure these contacts are excluded from outbound campaigns in Salesforce.

Splio Interactions are custom events sent via API to trigger loyalty point credits and other use cases. We export interaction event logs as Salesforce Task or Event records linked to the Contact. Event type, timestamp, and any payload fields migrate as custom fields on the activity record.

Splio custom fields are scoped per object type (contacts, stores, products, orders, rewards, loyalty). Each custom field has a defined scope in Splio. We export the custom field definitions during scoping, pre-create the equivalent custom fields on the matching Salesforce object, and then import data with the custom fields populated. Field types are mapped from Splio to Salesforce (text to text, number to number, date to date, picklist to picklist or multi-select picklist).

Order-scoped custom fields in Splio migrate to custom fields on the Salesforce Opportunity object. These are created in the schema design phase before Opportunity import begins.

Splio Owner references on contacts, orders, and loyalty memberships map to Salesforce User by email match. Owners without a matching Salesforce User go to a reconciliation queue for admin provisioning before record import resumes.