Migrate from Splio to monday CRM

Splio Contacts map to Contact Items on a Monday.com CRM Board. We resolve the list-membership exclusion by auditing every Splio contact before export: contacts without any list assignment are flagged as orphans, assigned to a catch-all segment, and re-exported to ensure full coverage. The Splio contact email field becomes the Contact Item's email column; first_name and last_name map to name columns. Custom contact fields (phone, address, birthdate) map to Monday.com text, number, or date columns as appropriate.

Splio Orders map to Deal Items in Monday.com CRM. Each Splio order links to a contact (which must migrate first) and carries order_id as the dedupe key. Monday.com does not have a native order object, so we create a Deals Board where each Item represents an order, with columns for order_id, order_date, total_amount, currency, and status. The Order-to-Contact relationship becomes a Connect board column linking the Deal Item to the Contact Item.

Splio order_items (individual line items) map to Subitems on the corresponding Monday.com Deal Item. Each subitem carries product_name, quantity, unit_price, and total_price. Subitem ordering is preserved by the creation sequence. This requires the parent Deal Item to exist before subitem creation; we sequence the order import before any subitem batch.

Splio Products are standalone items referenced by order_items. We create a Products Board in Monday.com with Items for each product, carrying sku (hs_sku), product_name, price, and any custom product fields from Splio's products scope. Products are migrated before order_items so that product references can be resolved at subitem creation time.

Splio loyalty memberships carry card_code, q_points (quantized balance), nq_points (non-quantized balance), and tier. Monday.com CRM has no native loyalty object. We create a dedicated Loyalty Board with Items linked to Contact Items via a Connect board column. Columns capture card_code (text), q_points (number), nq_points (number), and tier (status column with tier values). Point values migrate as numeric; the customer configures any redemption logic or tier thresholds in Monday.com after migration.

Splio rewards are defined at the program level; attributions track which contacts received which rewards. We map reward definitions to a Rewards Board (as reference data) and reward attributions to a Rewards Attribution Board linked to both the Contact and the Reward. This is a configuration mapping: the semantic meaning of each reward migrates; the redemption automation is documented for the customer to rebuild in Monday.com automations.

Splio Store records represent physical retail locations and e-commerce sites. We create a Locations Board in Monday.com with Items for each store, carrying store_name, address, city, country, and store_type (status column: physical, ecommerce). Store locations are referenced by Splio order records; we preserve the store reference as a Connect board column or status column on the related Deal Item.

Splio Interactions are custom events sent via API for loyalty point credits and campaign triggers. We export interaction event logs as a record set and map them to a dedicated Activity Board in Monday.com, with columns for event_type, timestamp, contact reference, and event_payload. If the customer requires a native-looking activity timeline on the Contact Item, we configure a connected Activity Board linked via Connect column. Interaction event type values become Activity Board Items.

Splio Lists drive contact segmentation and export eligibility. We preserve list memberships as Tags on Contact Items in Monday.com CRM. The tag-based approach mirrors Splio's list logic and is filterable via Monday.com's group and filter features. Blocklists migrate as a separate Suppression Board; any imported contacts matching blocklist email addresses are flagged before insertion and reported in the reconciliation manifest.