Migrate from Insider to Pipedrive

Insider User profiles contain both individual contact attributes (email, phone, name) and company-level properties (company name, industry, employee count). We split these during transformation: individual attributes map to Pipedrive Person; company-level attributes map to a Pipedrive Organization, and we link the Person to the Organization via the org_id field. If a User has no company attribute, the Person is created without an Organization link.

Insider allows arbitrary key-value custom properties per User beyond the standard profile schema. We export all custom attributes as flat key-value pairs, then create equivalent custom fields in Pipedrive on the Person object (or Organization if the attribute is company-scoped). Pipedrive's custom field limits vary by plan: Lite supports a limited set, Growth and above support more. We configure all custom fields before migration and validate that all Insider custom attribute names are valid Pipedrive field labels.

Insider Events are first-class objects with event_name, timestamp, and event_parameters. Pipedrive has no native behavioral event object. We reconstruct the event stream as Pipedrive Note records attached to the relevant Person, with the Note body containing event_name, timestamp, and a formatted dump of event_parameters. For high-volume event streams, we group events by day and create one Note per day per user to avoid creating thousands of individual Notes, with the Note body containing a structured event log. This preserves the data for audit and reporting even if the native timeline experience differs from Insider.

Insider Segments are defined by attribute rules and event conditions against the CDP. We export the member list (User IDs) and the segment's rule definition as metadata. Pipedrive has no dynamic segment equivalent; we recreate segment membership as a static filter on Person using the filter API, or by creating a custom Person field (e.g., insider_segment__c) and populating it with the segment name so that the customer's admin can filter Pipedrive Persons to match the original segment membership.

Insider User tags are arbitrary string labels stored as an array per User. Pipedrive supports Labels on Person records. We map each Insider tag to a Pipedrive Label. If the customer has more tags than Pipedrive Labels can accommodate at their plan tier, we discuss an alternative using a multi-select custom field or a Tag-like custom field approach.

Insider Lists are static user collections separate from dynamic Segments. We export list membership (user_id + list_id) and recreate each list as either a Pipedrive Person filter using the filter API or as a custom Person field (e.g., insider_list__c) with the list name as the value. The choice depends on the customer's Pipedrive plan tier and whether filters are supported.

Insider Product catalog data (sku, name, price, category, images, custom attributes) maps directly to Pipedrive Product. We preserve ProductCode from the sku field, pricing data, and any product-level custom fields as Pipedrive Product custom fields. Product images are not stored in Pipedrive's native image field, but the Product record is created with a link to the source image URL in a custom field.

Insider Transaction records (order_id, total, items, currency, timestamps) map to Pipedrive Deals with Line Items. Each transaction becomes a Deal with the total amount mapped to Deal value, order_id stored in a custom field, and individual transaction items mapped to Deal Products (line items). Currency is preserved. If the transaction references a Person (the purchaser), we link the Deal to that Person via the Person ID; if it references a company, we link to the corresponding Organization.

Insider Journeys are multi-step event-driven workflows with entry triggers, conditional gates, and channel actions. Insider provides no API endpoint to export Journey definitions. We export a full journey audit during discovery: every active Journey is documented with its trigger, conditions, steps, and channel actions in a written deliverable. Pipedrive's Automation rules (trigger-action pairs) are then rebuilt manually by the customer's admin using this documentation. The migration itself does not recreate the automation logic.

Insider's native SMS sender IDs, WhatsApp Business Account credentials, email sender domains, and push notification credentials are platform-specific infrastructure that cannot be transferred to Pipedrive. Pipedrive integrates with external SMS providers (Twilio, MessageBird) and email via SMTP or its native email sync. We document the customer's existing channel configurations in the discovery deliverable and flag which providers require new setup in Pipedrive. Email templates and WhatsApp message templates are not migratable and require rebuild.

Insider Owners (users with access to the platform) map to Pipedrive User records. We resolve Owners by email match against the Pipedrive destination User table. Any Insider Owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes.