Migrate from InTouch to Pipedrive

InTouch contacts map directly to Pipedrive People. The primary company from InTouch becomes the org_id on the Pipedrive Person record, linking each contact to its corresponding Organization. If a contact has no company assignment in InTouch, it is imported as a standalone Person record without an org_id. All original InTouch identifiers are preserved in a custom Source_ID__c field for traceability and subsequent delta runs.

InTouch companies translate to Pipedrive Organizations. Company name maps to Organization name, domain to the website field, and address components (street, city, state, postal code, country) populate the Organization address block. Parent-child hierarchies present in InTouch are reproduced using Pipedrive's Parent Organization field, preserving the corporate structure. All InTouch company IDs are stored in a custom Source_ID__c field for reference and de-duplication during incremental loads.

InTouch deals map to Pipedrive Deals. The deal name becomes the Deal title, amount maps to value, and the InTouch stage name maps to a Pipedrive stage_id within the target pipeline. Owner resolution happens via email match to Pipedrive users.

Each InTouch pipeline is replicated as a Pipedrive Pipeline. Before loading deals, we create the pipeline in Pipedrive, configure its stages with order and probability values, and set any stage-specific settings. During deal migration, InTouch stage names are mapped value-by-value to the created Pipedrive stage IDs, ensuring each deal lands in the correct pipeline and stage. This pre-creation step prevents missing stage references and allows deal placement from the start.

InTouch stage names are mapped value-by-value to Pipedrive stage names within the target pipeline. Each InTouch stage's probability percentage is transferred to the corresponding Pipedrive stage probability setting where available; if the probability data is missing, default values are applied and can be adjusted later. This mapping preserves the original deal progression logic and ensures that deal forecasting reflects the historical stage distribution after migration.

InTouch logged calls, emails, and tasks migrate as Pipedrive Activities with matching type (call, email, task). Original timestamps, due dates, and owner assignments are preserved. Activities linked to specific deals in InTouch connect to the corresponding Pipedrive Deal via deal_id.

InTouch meetings map to Pipedrive Activities with type='meeting'. The meeting's start time, end time, location, and attendee list from InTouch are recorded in the corresponding Pipedrive Activity fields, preserving the full scheduling details. After migration, you can reconnect Google Calendar or Outlook integrations in Pipedrive to enable live two-way sync for new meetings, while historical meeting data remains intact within the Activity timeline.

InTouch notes attached to contacts, companies, or deals become Pipedrive Notes linked to the corresponding Person, Organization, or Deal record. Rich-text formatting—such as bold, italic, bullet lists, and hyperlinks—is preserved where InTouch supports it, ensuring visual hierarchy and embedded links remain readable in Pipedrive. Plain-text notes are loaded directly into the Note content field. All notes retain their original creation timestamps and owner assignments for a complete audit trail.

InTouch custom fields require pre-creation in Pipedrive before migration. We map field types (text, number, date, picklist) to equivalent Pipedrive field types. Pipedrive assigns hash-based keys on creation — we capture these and use them for subsequent data loads. Picklist values are mapped value-by-value.

InTouch tags applied to contacts, companies, or deals become Pipedrive Labels. Labels exist per entity type in Pipedrive (Person Labels, Organization Labels, Deal Labels) and are color-coded for visual filtering. Multi-value tags on a single record become multiple Label assignments in Pipedrive.

InTouch users and deal owners are matched to Pipedrive users by email address. Unmatched owners are flagged before migration — teams either invite the user to Pipedrive first or assign records to a designated fallback owner. User-specific settings (notifications, visibility) require post-migration configuration in Pipedrive.

InTouch file attachments associated with contacts, companies, or deals are downloaded from InTouch and re-uploaded to Pipedrive Files, where they are linked to the corresponding Person, Organization, or Deal record. The original file names, sizes, and upload dates are preserved to maintain document history. InTouch file size constraints are respected during extraction, and Pipedrive's storage limits per plan are observed after load, with optional bulk storage upgrades if needed.