Migrate from Splio to Nutshell

Splio Contacts map to Nutshell People. The critical migration step is Splio's list-membership exclusion: any Splio contact without at least one list assignment is silently skipped during export. We run a list-membership audit during scoping, flag orphan contacts, assign them to a catch-all list, and verify the post-export count matches the full contact total before declaring migration complete. Contact email, name fields, phone, address, and any contact-scoped custom fields migrate directly.

Splio Store records representing business entities map to Nutshell Account. Store name becomes Account name; store address maps to billing address fields. If the Splio customer used contacts linked to store locations (rather than true company records), we create Account records from the store location data during migration. Account custom fields migrate from Splio's stores scope.

Splio Deals map to Nutshell Opportunities. Deal name, amount, stage, expected close date, and owner migrate directly. Splio Deal stages map to Nutshell pipeline stages. If Splio Deals carry order_id references, we store the original Splio order_id in a Nutshell custom text field for audit. Splio does not have a native opportunity pipeline object; deals exist as a flat list with a stage property, so we create a Nutshell pipeline structure before migration.

Nutshell has no native order object. Splio Orders (with order_id, contact reference, total amount, order_items) are migrated as Opportunities with custom fields capturing order metadata: order_id in a text field, order total in amount, and order date in a custom date field. Order_items are summarized in the Opportunity description or a custom long-text field. If the customer requires granular line-item history, we document the order_items schema separately for them to evaluate Nutshell custom objects or a third-party quoting tool.

Splio Products are standalone items referenced by order_items. Nutshell has no native product catalog. We assess whether the customer needs product-level reporting. If yes, we create a Nutshell custom object Product with fields for name, SKU, price, and category, and link it to the Opportunity via a lookup relationship. If product history is minimal, we store product name as a text field on the Opportunity.

Splio Loyalty memberships carry card_code, q_points (quantized points), nq_points (non-quantized points), and tier. Nutshell has no native loyalty object. We map these to Person custom fields: card_code__c (text), loyalty_points__c (number), loyalty_tier__c (text), and membership_date__c (date). Points balance and tier history are static snapshots at migration time; ongoing loyalty accrual requires rebuilding in a loyalty platform or custom Nutshell integration post-migration.

Splio Rewards are defined at the program level; attributions track which contacts received which rewards. Both map to Person custom fields in Nutshell: reward_name__c (text), reward_date__c (date), reward_status__c (text). The reward definition itself (program rules, point values, tier thresholds) is not a record-level object and does not migrate; we deliver a written reward program inventory for the customer's admin to document in a knowledge base or rebuild in a loyalty platform.

Splio Interactions are custom API events used to trigger loyalty point credits and campaign triggers. Nutshell does not support a generic custom event object. We export interaction event logs as Activity records: Task records with a custom interaction_type__c field and the original Splio timestamp preserved in ActivityDate. The customer receives a written inventory of all distinct interaction event types for their admin to evaluate whether Nutshell's standard Task model or a third-party CDP integration suits their needs.

Splio Lists drive contact segmentation and export eligibility. List memberships migrate to Nutshell as tags on People (Nutshell's native tagging) or as a multi-select custom field split_list__c if the customer prefers structured field storage over tags. Blocklists migrate as a Person custom field opt_out__c set to true for suppressed contacts.

Splio Users referenced on Contacts, Deals, and Loyalty memberships map to Nutshell Users by email match. We resolve every distinct owner email against the Nutshell destination tenant's User table. Any Splio owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes.