Migrate from Insightly CRM to Pipedrive

Insightly Organizations map to Pipedrive Organizations (the Company object). We import Organizations first in every migration because Contacts reference them as a parent lookup. The Organization record serves as the canonical Account-level record in Pipedrive and must exist before any Person record that references it.

Insightly Contacts map to Pipedrive People. Standard fields (name, email, phone, address) migrate directly. We sequence Contact import after Organization creation so that the OrganizationId relationship resolves at insert time. Insightly's explicit link records connecting Contact to Organization are reconstructed in Pipedrive by setting the Person's Organization field during import.

Insightly Leads are top-level records with their own lifecycle. We map them to Pipedrive People with a custom field is_lead__c set to true to preserve the original Lead classification. If the customer wants Leads managed separately in Pipedrive, we create a separate Pipeline and stage naming convention to represent the lead status; this is decided during scoping.

Insightly Opportunities map to Pipedrive Deals. Each Deal is linked to the corresponding Person and Organization. Stage names in Insightly are freeform strings that must map to Pipedrive stage names; we build a stage mapping table during discovery and apply it across all Opportunity records. Probability and monetary value migrate as custom or standard Deal fields depending on Pipedrive's current field configuration.

Insightly pipeline stages are custom-named strings. Pipedrive requires stages to be pre-created inside a Pipeline object. We collect every distinct stage name in the source account during discovery, present the customer with a stage mapping table for approval, create the corresponding Pipedrive Pipeline and stages before any Deal import, then apply the mapping across all records during migration.

Insightly Tasks linked to any primary object map to Pipedrive Activities attached to the corresponding Deal, Person, or Organization. Task status values (Not Started, In Progress, Completed, Deferred) map to Pipedrive Activity status values. The due date and assigned owner migrate directly; owner resolution uses email-based matching against Pipedrive Users.

Insightly Notes are standalone objects that can link to any primary record. They map to Pipedrive Notes attached to the Person, Organization, or Deal. We preserve note body, author, and creation timestamp. The link relationship to the parent record is reconstructed by matching the source record ID against the migrated destination ID during the Notes phase.

Tags in Insightly are flat string labels applied to Contacts, Organizations, Opportunities, and Projects. They map directly to Pipedrive Labels, which apply to People, Organizations, and Deals. Tag arrays export as string lists and import as Label associations. Label semantics are preserved as-is; Pipedrive Labels function identically to Insightly Tags.

Insightly Custom Objects with their own fields map to either Pipedrive Custom Fields on standard objects (Lite through Premium) or Pipedrive Custom Objects (Premium and Ultimate tiers only). We pre-create the destination schema before migration, validate field types (text, date, picklist, currency), and map Custom Object records accordingly. If the customer is on a lower Pipedrive tier, Custom Object data merges into a designated standard object with a type discriminator field.

Insightly attachments are stored as URL or blob references. We do not migrate attachment binary data. We export attachment metadata (filename, URL, associated record type and ID) and reconstruct it in Pipedrive as Note records with the original filename and URL preserved. The customer's admin confirms whether binary file migration is required as a separate file transfer task.