Migrate from Interactive to Pipedrive

Contacts map to Pipedrive People field-for-field. Owner assignment requires email-based matching to Pipedrive users — unmatched owners flagged before migration commits. Original create dates from Interact migrate as a custom datetime field (Original_Create_Date__c equivalent) since Pipedrive sets CreatedDate at import time.

Companies map 1:1 to Pipedrive Organizations. Parent-company hierarchies in Interact map via Organization.ParentId — the parent organization must migrate first; circular references are flagged and resolved by FlitStack before commit. Multi-company contact associations (Interacts N:N model) attach the primary company as the OrganizationId on the Person, with secondary companies surfaced via Organization Relationship records.

Deals map directly to Pipedrive Deals with stage values mapped per pipeline. Pipeline-to-pipeline 1:1 mapping requires Pipedrive pipeline and stages to be pre-created with matching names before the migration run. Stage probability and forecast category are reapplied from Pipedrive's stage configuration after stage-name mapping is confirmed.

Each Interact deal pipeline maps to one Pipedrive pipeline. Pipedrive pipelines must be created in Pipedrive Settings > Pipelines before migration — FlitStack delivers a setup checklist naming each Interact pipeline and its recommended Pipedrive stage count. Stage ordering from Interact is preserved as the display order in Pipedrive.

Stage names map value-by-value from Interact to Pipedrive. Probability percentages and forecast categories from Interact stage configuration are stored as custom fields in Pipedrive post-migration since Pipedrive's stage probability is controlled at the stage level. If a Pipedrive stage with a matching name does not exist, the migration plan flags it for admin creation before the run.

Interact's separate call, email, and meeting engagement records collapse into Pipedrive's unified Activity model, differentiated by the Activity type field (call, email, or meeting). Original timestamps, owners, and person/deal associations are preserved. Interact call duration and outcome flags map to Pipedrive Activity custom fields if configured.

Files attached to Interact contacts, companies, or deals are downloaded from Interact's storage and re-uploaded to Pipedrive's Files. File size limits from Pipedrive apply (25MB default per file on most plans). File associations to Person, Organization, or Deal records are reconstructed using Pipedrive's file linking API after upload. Inline images embedded in Interact notes are extracted and rehosted separately.

All Interact custom contact, company, and deal properties migrate as Pipedrive custom fields on the equivalent entity (Person, Organization, Deal). Pipedrive's API generates a random 40-character key for each custom field — FlitStack stores the Interact field name alongside the Pipedrive field key in the mapping manifest so the admin can reference which field is which. Field data types (text, number, date, pick-list) are matched during the discovery scan.

Interact owner IDs resolve to Pipedrive users via email address matching. Before migration, FlitStack queries the Pipedrive account's user list and matches each Interact owner email to an active Pipedrive user. Unmatched owners are reported in the pre-migration audit — the customer either invites them to Pipedrive or assigns a fallback user before the run. No deal or person record lands without a valid Pipedrive OwnerId.

Interact contact, company, and deal tags map to Pipedrive Labels. Labels are entity-specific in Pipedrive (a label set on a Person is separate from a label with the same name on a Deal). FlitStack preserves the entity context for each tag during migration so labels do not bleed across object types. Pipedrive's Label API creates labels on demand if they do not already exist in the destination account.

Interact quiz results and lead-capture form submissions are stored as custom fields on the Person record. These migrate as Pipedrive custom fields on the Person object. FlitStack identifies all quiz and form custom fields during discovery and pre-creates matching Pipedrive custom fields before the migration run. The field names in Pipedrive must match the Interact custom field labels for the import to succeed.

If Interact includes a numeric lead-scoring field on contacts, it migrates to a Pipedrive custom number field on Person. The field type must be set to 'number' in Pipedrive before migration; FlitStack flags the field type during discovery and includes it in the pre-flight setup checklist. Without this field pre-created, lead score values are logged in a text custom field as a fallback.

Interact notes attached to contacts, companies, or deals migrate to Pipedrive Notes. Pipedrive stores notes as HTML in its backend — FlitStack converts plain-text Interact note content to HTML before import, preserving line breaks and paragraph structure. Notes are linked to the correct Person, Organization, or Deal record using Pipedrive's content_id and content_type fields.