Migrate from Splio to HubSpot

Direct map. Splio contacts migrate to HubSpot contacts. Splio contacts without a list assignment are reconciled against the full contact export before migration to prevent exclusion. HubSpot requires at minimum an email address for contact creation; contacts without email are flagged for manual review.

Splio contacts with active loyalty memberships split into HubSpot Contact plus a Loyalty_Membership__c custom object linked by email. The custom object stores nq_points, q_points, tier, and card_code. HubSpot's association model links the custom object to the contact record. The association uses the contact's email as the primary key, ensuring queries can pull loyalty status directly from the contact record. This design maintains referential integrity and simplifies reporting on loyalty metrics.

Splio lists map to HubSpot static lists. Splio blocklists map to a HubSpot blocklist property on each contact. Dynamic lists built on Splio filters are not transferable — they require rebuilding in HubSpot with HubSpot's filter syntax. During migration, we preserve the static list membership by creating corresponding HubSpot static lists and populating them with the same contacts. The blocklist property is set as a boolean flag for quick suppression.

Splio products migrate to HubSpot products. The product name, SKU, price, and description map directly. HubSpot products must exist before line items reference them on deals, so products migrate before order data. If a Splio product lacks a SKU, we generate a placeholder SKU to ensure compatibility with HubSpot's product library. After migration, you can update product details directly in HubSpot's product management interface.

Splio store data (store name, location, store_id) attaches to HubSpot products via a custom property (Store_ID__c) for retail scenarios, or to companies for B2B branch tracking. We surface this mapping decision in the migration plan before data lands. This ensures that store attribution is searchable in HubSpot reports and can be used in downstream workflows such as regional segmentation or store-specific email campaigns.

Splio orders migrate as HubSpot deals. The order total becomes the deal amount. Order date maps to the deal close date. Each order_item links to the product record via a HubSpot line item. Splio order_id preserved as Original_Order_ID__c for reconciliation.

Splio order_items map directly to HubSpot line items. Quantity and unit price map to HubSpot Quantity and Unit Price. Line items reference the HubSpot product record by product ID. Order items without a matching product in HubSpot are flagged before migration.

Splio campaigns migrate as HubSpot campaigns. Campaign name, type, and scheduled date map directly. HubSpot campaigns track which contacts are members but do not carry Splio's internal engagement scoring — that requires rebuilding with HubSpot's lead scoring tool. To preserve historical campaign context, we also record the original Splio campaign ID as a custom property on the HubSpot campaign record for reference and future reconciliation.

Splio campaign events (opens, clicks, page views, behavioral triggers) have no native HubSpot equivalent. We preserve the most recent event type and timestamp as custom properties on the contact record. Full event history is exported as a JSON file and attached to the contact for reference.

Splio rewards (reward type, attribution date, expiry) migrate to the Loyalty_Membership__c custom object. Active reward attributions are preserved; expired rewards are flagged for archival based on your retention criteria. During migration, we map the reward type to a text field, the attribution date to a date property, and the expiry date to a separate expiration field. This structure enables future queries for active versus expired rewards.

Splio custom fields scoped to contacts migrate as HubSpot custom contact properties. Field type maps per Splio type: text → string, int → number, double → number, date → date. Pick-list fields in Splio become HubSpot dropdown properties. We also preserve any default values or validation rules defined in Splio by replicating them as property settings in HubSpot, ensuring data consistency after migration.

Splio custom fields scoped to orders migrate to HubSpot custom properties on the deal. Order-level custom fields (e.g., fulfillment_status) attach to the deal record; product-level custom fields on order_items attach to the line item. We map each custom field to the appropriate HubSpot property, preserving data types and any associated pick-list options. This ensures that order metadata remains searchable and reportable in HubSpot's analytics tools.

Splio filters used for segmentation have no HubSpot equivalent. We export the filter definitions as a reference document. HubSpot lists and smart lists must be rebuilt using HubSpot's filter builder. This is a manual rebuild item disclosed upfront. During the export, we capture filter criteria, operator logic, and any nested conditions so your team can replicate the logic accurately in HubSpot. This reference file is delivered alongside the migration deliverables.