Migrate from InTouch CRM to Pipedrive

InTouch CRM Contacts map to Pipedrive Person records. The contact's email address serves as the dedupe key during import. First name, last name, phone, email, address, and owner reference transfer directly. We flag any InTouch Contact without an email address for manual review before import because Pipedrive's Person model strongly correlates identity on email.

InTouch CRM Companies map to Pipedrive Organizations. Company name becomes the Organization name, and domain becomes the Website field if present. Organization must be imported before Person so that the Organization-Person link is satisfied at insert time. We resolve the link using company name matching with a fuzzy-match fallback for minor spelling differences.

InTouch CRM Deals map directly to Pipedrive Deals with deal value, title, stage, owner, expected close date, and created/modified timestamps preserved. We pre-create the Pipedrive pipeline and stages before Deal import so that stage labels can be mapped from InTouch's pipeline stage names to Pipedrive stage IDs at migration time.

Each InTouch CRM Pipeline becomes a Pipedrive Pipeline. Stage names and probabilities transfer from InTouch and are recreated as Pipedrive stage entries with the same order and probability percentages. Pipedrive allows stage probabilities to be customized per stage; we preserve InTouch's probability values or use sensible defaults if the source data is sparse.

InTouch call activities map to Pipedrive Tasks with TaskSubtype = Call. Subject, duration, disposition, and original timestamp transfer. The task is linked to the Person or Deal record that was the parent in InTouch. We batch-call activities in groups of 200 to stay within Pipedrive's write rate limits and retry with exponential backoff on 429 responses.

InTouch email activities migrate as logged activities in Pipedrive. Subject, body (plain text or HTML), direction (sent/received), and timestamp transfer. The activity links to the Person or Organization that was the sender or recipient. Pipedrive does not store raw MIME email files; we preserve the email subject, body content, and timestamp, and note that the full email thread view requires the Gmail or Outlook integration post-migration.

InTouch meeting activities map to Pipedrive logged activities with the meeting title, description, start time, duration, and attendees preserved. Attendees are stored as free-text in the activity body if the InTouch schema stores them separately; we consolidate them into the activity note field for readability.

InTouch standalone task activities map to Pipedrive Tasks with subject, due date, status, priority, and owner preserved. The owner maps via email resolution to the matching Pipedrive user. Completed status maps from InTouch's completion flag to Pipedrive's Task status field.

InTouch CRM custom fields must be pre-created in Pipedrive before any record import begins. We extract the full custom field list during scoping, map each to the closest Pipedrive field type (text, number, date, dropdown, checkbox, address), create them in Pipedrive via API, and then map values during the data transform phase. Dropdown and picklist fields require value-level mapping in addition to field-level mapping.

InTouch CRM Owners map to Pipedrive Users by email address match. We extract every distinct owner referenced on Contacts, Companies, Deals, and Activities and resolve each against the destination Pipedrive account's user list. Any owner without a matching Pipedrive user goes to a reconciliation queue for the customer's admin to provision before import resumes.