Migrate from Insider to Freshsales

Insider user profiles map to Freshsales Contact by default, with a Lead split for profiles that have not yet entered a sales-qualified stage. We evaluate the insider_hs_lifecyclestage property and any custom stage indicator to determine whether a record should land as a Lead or Contact. Standard profile fields (email, phone, first_name, last_name) map directly. All custom user attributes from Insider become Freshsales Contact custom fields, which we pre-create in Freshsales before migration begins. The mapping type is 1:N split because a single Insider user may need to create both a Lead record and, upon conversion, a Contact record in Freshsales.

Insider behavioral events (page views, purchases, cart actions, custom events) migrate to Freshsales Task records with TaskSubtype set to the event category. Each Task captures event_name, timestamp, and event_parameters as a JSON-serialized custom field on the Task. This is not a perfect behavioral profile representation — Freshsales does not have an event stream model — but it preserves the activity timeline in a searchable, reportable form. Events without a resolvable Contact email are held in a quarantine queue for admin resolution before import.

Insider segment membership (the list of users in a given segment) migrates to Freshsales Static Lists. We export the member email and segment ID, then recreate the segment as a Freshsales contact list. The segment's rule definition — the attribute conditions and event triggers that define membership — does not migrate because Freshsales Groups do not support the same rule engine. We document each segment's rule logic in a written inventory deliverable so the admin can recreate active segments using Freshsales' filter and list conditions. The mapping type is 1:1 at the membership level, not the definition level.

Insider custom user properties beyond the standard profile schema (arbitrary key-value pairs stored in the CDP) become Freshsales Contact custom fields. We pre-create each custom field in Freshsales before migration using the Freshsales REST API, inferring field type from the property value (string, number, date, boolean). Multi-value arrays (arrays of tags or IDs) map to Freshsales multi-select picklists or text fields depending on the array contents. Any custom attribute that references an Insider-specific object (a channel identifier or a journey ID) is flagged during scoping and migrated as a text field with a note that the reference requires manual cleanup.

Insider product catalog entries — sku, name, price, category, images, and custom attributes — map directly to Freshsales Product records. The sku becomes Product Code, name becomes Product Name, price maps to Unit Price, and category becomes a custom Product Category field. Product associations with Insider transaction events migrate as Line Items under Freshsales Deals if the corresponding Deal exists for the associated user account.

Insider transaction objects (order_id, total, items, currency, timestamps) migrate to Freshsales Deals with the amount field populated from the transaction total and the close date set from the transaction timestamp. Individual line items within a transaction migrate as Freshsales Deal Line Items linked to the parent Deal. Currency mapping preserves the original currency code, and amounts are stored in Freshsales' currency fields without automatic conversion. Deals created from transactions are flagged with a source: insider_transaction custom field to distinguish them from pipeline Deals created natively in Freshsales.

Insider static lists — named user collections beyond dynamic segment membership — migrate to Freshsales Static Lists. We export the list membership records (user email + list ID), resolve each email to a Freshsales Contact, and add the Contact to the corresponding Freshsales list. Lists with no corresponding Freshsales Contact are recorded in the reconciliation report for admin review. List names and descriptions migrate as list metadata.

Insider user tags (arbitrary string labels applied to profiles) migrate as Freshsales Contact tags. We evaluate whether the customer's tagging taxonomy is better represented as Freshsales native tags or as a custom multi-select picklist field during scoping. For high-cardinality tagging systems (more than 50 distinct tag values), we recommend a custom field approach to avoid tag sprawl. Tags that encode behavioral signals (engagement tier, risk flag) are migrated to a dedicated Freshsales custom field rather than a generic tag so that they can trigger workflow conditions.