Migrate from Intrix CRM to Pipedrive

Intrix Client records migrate 1:1 to Pipedrive Organizations. We extract Client name, industry, contact information, and any custom fields stored against the Client record. The Client's 360-degree overview data and address fields map to Pipedrive's Organization standard fields. Client ID is preserved as a custom field org_intrix_id__c for deduplication and audit. If the Client has associated Contacts, we import Organizations first so that the Organization can be resolved before Person records land, avoiding orphaned Persons without a parent Organization.

Intrix Contact records migrate to Pipedrive Persons with the Client-Client relationship mapped to Pipedrive's Organization field on Person. We match each Contact to its parent Organization by Intrix Client ID or Client name. Contact name, email, phone, role, and any custom contact-level fields transfer to Pipedrive Person fields. Persons without a resolvable Organization are imported with Organization left blank and flagged for manual association after the Organization import phase completes.

Intrix Opportunities map to Pipedrive Deals. We transfer deal title, value, expected close date, owner assignment, and the current pipeline stage. Intrix's pipeline stage names are customer-specific and do not match Pipedrive's default stage values (Prospect, Qualification, Proposal Sent, Negotiation, Won, Lost). During scoping we extract the customer's active stage configuration and map each Intrix stage name to the equivalent Pipedrive stage in the customer's pipeline, creating new stages where no direct equivalent exists.

Intrix's configurable pipeline stage model maps to Pipedrive's Pipeline and Stage objects. We extract the customer's complete stage list including stage order, probability percentages, and any stage-specific actions. Each Intrix pipeline maps to a Pipedrive Pipeline with its own Stage list. If Intrix uses multiple pipelines, we create corresponding Pipedrive pipelines and assign deals to the correct pipeline during migration using the pipeline ID resolved from the stage mapping.

Intrix Activities logged against Clients or Opportunities migrate to Pipedrive Activities. Call logs become Pipedrive Activities with type=call and the call outcome preserved in a custom field. Email activities transfer with the full email body and timestamp as Activity entries. Meeting records migrate with date, duration, and location. Task-type activities map to Pipedrive Activities with type=task and status=done or open matching the original Intrix completion state. All Activities are linked to the correct Organization and Person using the relationship IDs resolved during the Organization and Person import phases.

Intrix Projects migrate to Pipedrive Projects using Pipedrive's Projects API. Each Intrix Project becomes a Pipedrive Project with its name, description, start date, and deadline transferred. The project owner maps to a Pipedrive user. We create Pipedrive Project Boards, Phases, and Project Templates as needed to mirror the Intrix project structure. Projects are imported before their associated tasks so that the project ID exists when tasks are written.

Intrix Tasks with predecessor dependencies require sequenced import into Pipedrive Project Tasks. We extract the dependency graph during data profiling and order the task imports so that a task's parent (predecessor) lands before the dependent task. Pipedrive's Project Task API accepts a predecessor reference; we reconstruct the dependency chain during import. Tasks without dependencies import in standard order. The task status, deadline, assignee, and estimated hours transfer to the corresponding Pipedrive Project Task fields.

Working Hours Records exist only on Intrix Advanced and Unlimited tiers. Pipedrive has no native time-tracking or Working Hours object. We migrate WHR data as a set of custom fields on the Organization or Person record (whichever the customer used WHR against), or as a separate custom entity if the destination Pipedrive plan supports custom objects. WHR entries include date, hours worked, and employee reference; these map to custom date, numeric, and text fields in Pipedrive. WHR is scoped out entirely if the source account is on Intrix Basic and has no WHR data present.

Intrix custom fields on any object migrate to Pipedrive custom fields of equivalent type. Text fields map to Pipedrive text fields, numeric fields to number fields, date fields to date fields, and picklist fields to Pipedrive dropdown fields. We extract the full custom field schema per object during scoping and pre-create the equivalent Pipedrive custom fields before any data import begins. Unsupported field types (such as Intrix-specific relational fields) are documented for the customer's admin to evaluate post-migration.

Intrix User records including access levels and role assignments migrate as owner references on Opportunities, Projects, and Tasks. We match Intrix users to Pipedrive users by email address. Any Intrix user without a matching Pipedrive user is placed in a reconciliation queue; the customer's Pipedrive admin provisions the missing user before the owner assignment phase runs. Inactive Intrix users are migrated as inactive Pipedrive users with their records assigned to them for historical accuracy.

Intrix attachments stored per Client, Contact, or Project are downloaded as individual files and re-uploaded to the corresponding Pipedrive record. The file name and any attached notes or descriptions are preserved as the attachment title. Large attachment sets require sequential upload to avoid Pipedrive API rate limit responses; we implement exponential backoff on attachment upload operations. We document the complete file inventory during scoping so that no file is overlooked in the migration.