Migrate from Visionary to Pipedrive

Visionary persons map directly to Pipedrive People. Every standard field (name, email, phone, address, job title) has a direct Pipedrive equivalent. Visionary persons linked to an organization map to Pipedrive People linked to the matching Organization record — the org must be migrated first so the link resolves at write time.

Visionary organizations map to Pipedrive Organizations. Field-level mapping covers name, domain, industry, employee count, and annual revenue. Parent-child org hierarchies in Visionary map to Pipedrive's Organization hierarchy using the parent_org_id field. Multi-company associations collapse to the primary org link with secondary associations stored as relationship fields.

Visionary deals map to Pipedrive Deals with one critical pre-condition: the target Pipedrive pipeline and all its stages must exist in Pipedrive before the migration runs. FlitStack delivers a pipeline-creation guide specifying the exact stage names and order so the deal stage values map cleanly to the correct PipelineStageId.

Visionary pipeline definitions become Pipedrive Pipelines. Each Visionary pipeline is created as a separate Pipedrive Pipeline with its own ordered stage list. Pipedrive allows multiple pipelines; Visionary pipelines map 1:N to Pipedrive pipelines with stage name mapping defined per pipeline. The pipeline's default flag determines which pipeline new deals route to by default.

Visionary stage names map to Pipedrive Stage names value-by-value per pipeline. FlitStack generates a stage-mapping matrix that your Pipedrive admin applies before the migration runs. Probability and forecast category values are set per stage in Pipedrive's pipeline settings — these are destination-side configuration, not migrated data, but FlitStack documents the Visionary stage-close rates to guide those settings.

Visionary custom person properties require pre-created custom fields in Pipedrive before migration. FlitStack generates a Pipedrive field-creation checklist with the exact field name, type (text, varchar, int, double, enum), and option list for pick-list fields. Visionary multi-select pick-lists map to Pipedrive multi-select fields; single-select maps to Pipedrive's single-option enum. The Pipedrive field hash key (e.g. dfb3473ac...) is discovered after creation and used in the field mapping plan.

Deal-level custom properties from Visionary migrate as Pipedrive Deal custom fields. The same pre-creation requirement applies: Pipedrive custom fields must exist before data writes. FlitStack delivers a deal-field creation checklist covering all Visionary custom deal properties with their type mappings so Pipedrive's schema is ready before the migration run.

Visionary engagement records (calls, emails, meetings) map to Pipedrive Activities. Each activity retains its type (call, email, meeting), subject line, original timestamp, and due date. The parent link (person_id or deal_id) is resolved against the migrated Visionary records using the source record ID preserved as a custom reference field, ensuring the activity appears on the correct Pipedrive record.

Visionary notes migrate to Pipedrive Notes with the original body text and author preserved. The note's create timestamp is set from Visionary's original create date. Notes linked to a Visionary person or deal re-link to the corresponding Pipedrive Person or Deal using the source record ID cross-reference stored in a custom field.

Visionary file attachments are downloaded and re-uploaded to Pipedrive Files, linked to the target Person, Organization, or Deal record. Pipedrive's file storage uses its own file server; Visionary attachment URLs do not persist after migration. FlitStack logs the original file name and Visionary attachment URL in a custom field on the Pipedrive record for audit traceability.

Visionary owner IDs do not map directly to Pipedrive user IDs. FlitStack resolves each Visionary owner by matching their email address against Pipedrive user accounts. Owners with no matching Pipedrive user are flagged before the migration runs — your Pipedrive admin creates the user account or assigns a fallback owner before the migration commits. No record migrates with an unresolved owner.