Migrate from Splio to Pipedrive

Splio Contacts map directly to Pipedrive People. We run a list-membership audit before extraction to identify any contact records without list assignment—these are silently excluded from Splio's standard export mechanism. We flag orphan contacts and either assign them to a catch-all segment or document them separately so the customer decides whether they travel with the migration. Email address, phone, and name fields map 1:1. Any Splio contact custom fields (scope: contacts) migrate as Pipedrive custom fields on Person.

Splio Loyalty memberships carry card_code, nq_points (non-quantized points), q_points (quantized points), and tier name. These fields have no native Pipedrive equivalent, so we create custom fields on Person: loyalty_card_code (string), loyalty_q_points (number), loyalty_nq_points (number), loyalty_tier (picklist with tier names from Splio). We resolve each membership to its linked contact during the import phase using the Splio contact_id reference.

Splio Store records represent physical retail locations and e-commerce sites. We map these to Pipedrive Organization. The Splio store name becomes the Organization name, and store address attributes map to the corresponding Pipedrive address fields. Any store-level custom fields (scope: stores) migrate as Organization custom fields. Store-to-contact relationships (which Splio uses for retail loyalty attribution) are preserved as Organization-Person links in Pipedrive.

Splio Products are standalone items referenced by order_items. They map to Pipedrive Products with name, SKU (mapped from Splio product code if present), and price. We create Pipedrive Product entries during the pre-import schema setup phase so that order_items can reference them at migration time.

Splio Orders link to a contact and carry order_items referencing products. Pipedrive has no native order object, so we map orders to Deals with the Splio order_id stored in a custom deal field (splio_order_id). Order total, currency, and status migrate to the deal's value and custom fields. Order_items are summarized in a deal-linked Activity note or expanded as custom deal line item fields. The deal's linked Person resolves the Splio contact_id.

Splio order_items are tied to a parent order via a required link. Splio rejects any order_item if the linked order does not exist. We sequence the migration so that Deals are created first (resolving parent order), then order_items are processed as structured text appended to the deal note or as individual custom fields. Product references resolve via the Product mapping.

Splio Rewards are defined at the program level and carry reward type, description, and point cost. Reward attributions track which contacts received which rewards. Neither has a native Pipedrive equivalent. We map reward definitions to a custom field reward_eligible (picklist with reward names) on the Person object, and store attribution history as a structured text custom field reward_history. Customers with complex reward logic receive a written specification for a custom Pipedrive app if native fields are insufficient.

Splio Interactions are custom events sent via API to trigger loyalty point credits and campaign responses. These are event objects in Splio's CDP schema. We export interaction event logs as Pipedrive Activity records (note type) linked to the Person, with the interaction type and timestamp preserved in custom fields. Interaction metadata migrates as structured text for audit purposes.

Splio Lists drive segmentation and campaign targeting. Pipedrive has no direct list object, so we map list memberships to Pipedrive Tags. Each Splio list becomes a tag, and contacts inherit all applicable tags on import. Blocklists in Splio map to Pipedrive's duplicate and spam prevention fields and a suppression tag that is honored during any future outbound setup.

Splio users who are assigned as owners of contacts, orders, and other records map to Pipedrive Users by email match. We extract all distinct owner references from the source export, match against the provisioned Pipedrive User list, and hold any unresolved owners in a reconciliation queue for the customer's admin to provision before record import resumes.

Splio campaign configurations, filter targets, trigger conditions, and email/SMS content do not migrate as functional code. Pipedrive's automation tools (Workflow Automation on paid plans) are a different execution model and cannot receive a direct Splio campaign export. We deliver a written inventory of every active Splio campaign with its trigger, conditions, target list, and recommended Pipedrive Workflow equivalent for the customer's admin to evaluate and rebuild post-migration.