Migrate your Splio data

Contacts export cleanly but Splio silently excludes any contact not assigned to at least one list. We flag these orphan contacts during scoping, assign them to a catch-all segment, and verify the post-import count matches pre-export totals. System fields (email, phone, preferences) map 1:1; custom contact properties require scope-aware field declaration.

Orders are the most structurally complex object—each order links to a contact and carries order_items referencing products. Splio replaces an existing order if the same order_id is re-imported and deletes all prior line items. We detect order ID collisions during the planning phase and surface the replacement behavior to the customer before migration.

Order_items (individual line items within an order) are tied to the parent order via a required link. Splio will reject any order_item record if the linked order does not already exist. We sequence order_item migration after order migration and validate the parent-child linkage on every batch.

Products are standalone items referenced by order_items. The platform supports product-level custom fields via the products scope. We export product attributes and map them to the destination's product or item object, preserving pricing and categorization fields where present.

Memberships carry the card_code, nq_points (non-quantized), q_points (quantized), and tier. Point balances are numeric but may include fractional values depending on program rules. We export the membership snapshot, map points to the destination loyalty engine's balance model, and flag any tier that requires a qualification threshold not present in the target.

Rewards are defined at the program level; attributions track which contacts received which rewards. Both objects interact with the Loyalty scope. We map reward definitions to the destination's reward catalog and preserve attribution history as a contact custom field or activity log.

Store records represent physical retail locations and e-commerce sites. The stores scope supports custom fields. We export store data with location attributes and map to the destination's equivalent location or store object, preserving any custom store-level properties.

Interactions are custom events sent via API to trigger specific use cases such as loyalty point credits. These are event objects in Splio's CDP schema. We export interaction event logs as activity records and map them to the destination's event or engagement timeline, noting that the triggering logic (automations relying on events) must be rebuilt.

Lists drive contact segmentation and export eligibility. We preserve list memberships as tags or segments in the destination. Blocklists are treated as suppression lists; we ensure these are honored during import to prevent bounced or blocked contacts from reactivating.