Migrate from Insightly Marketing to Pipedrive

Insightly Contact records map to Pipedrive Person. Standard fields (name, email, phone, address) migrate directly. Custom fields on Contact map to Pipedrive Person custom fields. The Insightly CONTACT_YOMIFULLNAME and similar localized name fields map to the appropriate name sub-fields in Pipedrive. Tags on the Insightly Contact are extracted and re-applied as Pipedrive Person labels.

Insightly Organization maps 1:1 to Pipedrive Organization. Organization name, domain, industry, phone, and address fields migrate directly. Organization-to-Contact links are preserved during migration by resolving the Person record after Organization insert. Custom fields on Organization map to Pipedrive Organization custom fields. We use Organization name as the dedupe key to prevent duplicate Organizations on re-migration attempts.

Insightly's separate Lead object splits into Pipedrive Leads and Persons based on qualification status. Insightly Leads with a status indicating they are unqualified or early-stage map to Pipedrive Leads. Leads with an associated Opportunity or advanced lifecycle stage in Insightly are converted to Pipedrive Persons attached to an Organization. We preserve the original Insightly lead status in a custom field on both the Pipedrive Lead and the Person record for audit continuity.

Insightly Opportunity maps to Pipedrive Deal. The pipeline and stage name from Insightly map to Pipedrive Pipeline and Stage. Stage probability values migrate as Pipedrive stage probabilities (rounded to integer). Expected close date, amount, and probability migrate directly. Custom opportunity fields map to Pipedrive Deal custom fields. The Organization relationship from Insightly Opportunity is resolved at migration time to attach the Deal to the correct Pipedrive Organization.

Insightly's pipeline configuration (stages, stage probabilities, stage order) maps to Pipedrive Pipelines. Each Insightly pipeline becomes a Pipedrive pipeline, and each Insightly stage becomes a Pipedrive stage in the corresponding pipeline. We configure stage probability percentages to match Insightly values. Closed-won and closed-lost stage handling in Insightly maps to the same semantic outcomes in Pipedrive.

Insightly Projects have no direct Pipedrive equivalent since Pipedrive does not include a native project management object. We migrate Project records as Pipedrive Activities (with a project-type activity category) and Notes attached to the related Organization or Deal for project context. Milestones migrate as separate Activity records with a milestone label. Customers requiring full project management functionality retain Insightly for project tracking or adopt a dedicated project tool post-migration.

Insightly Tasks map to Pipedrive Activities. Due date, assignee (resolved via owner email to Pipedrive User), status, and related object reference (Contact, Organization, Opportunity, or Project) migrate. Activity type is set based on Insightly task type. Tasks related to Insightly Projects are linked to the corresponding Activity or Note created from the Project record. Open and completed task status maps to the equivalent Pipedrive Activity status values.

Insightly custom fields on Contacts, Organizations, Opportunities, and Projects map to Pipedrive Person, Organization, Deal, and Activity custom fields respectively. We perform a type-mismatch review during mapping because Insightly supports date, numeric, text, picklist, and boolean custom field types, and Pipedrive imposes field-type restrictions at the account tier level. Multi-select picklist values from Insightly migrate to Pipedrive multi-select fields where available or to text fields with comma-separated values as a fallback.

Insightly custom objects (customer-defined schemas) have no direct Pipedrive equivalent since Pipedrive does not support custom object creation. We handle this by mapping each Insightly custom object to a set of Pipedrive custom fields on the closest standard object (Person, Organization, or Deal). For custom objects with relationships to multiple standard objects, we use Note records with structured content to preserve the related data and its associations.

Insightly tags on Contacts, Organizations, Opportunities, and Projects extract as a flat list of tag names per record. We re-apply these as Pipedrive Labels on the corresponding Person, Organization, or Deal record. Label assignment is resolved after Person and Organization inserts to ensure the parent record exists before the label is applied.