Migrate from Pure Chart to Pipedrive

Pure Chart contacts map to Pipedrive Person objects through a direct field correspondence. The email address serves as the primary unique identifier for de-duplication purposes. FlitStack cross-references each Pure Chart contact email against existing Pipedrive Persons before performing the insert operation, preventing duplicate records from being created during the migration process.

Pure Chart company records are transformed into Pipedrive Organization objects with a one-to-one mapping. Organization.Name is a required field in Pipedrive, so if the Pure Chart company name is absent or empty, FlitStack applies 'Unknown Organization' as a placeholder value to ensure data integrity and successful import completion.

The relationship between Pure Chart contacts and their associated companies maps directly to Pipedrive's Person.organization_id field on each Person record. When multiple contacts belong to the same organization, FlitStack links each corresponding Person record to the identical Organization identifier, preserving the original relationship structure.

Pure Chart deal records migrate as Pipedrive Deal objects with all standard fields preserved. Each Deal in Pipedrive requires both a Pipeline ID and a Stage ID at creation time. FlitStack maps Pure Chart deal stage values to the appropriate target Pipedrive pipeline stages by matching stage names or examining their ordinal position within the stage sequence.

Stage names defined in Pure Chart are mapped to corresponding Pipedrive stage names through string matching or an admin-defined mapping table provided before migration. Stages that cannot be matched to existing Pipedrive stages default to the first stage configured in the target pipeline, ensuring every deal receives a valid stage assignment during import.

Pure Chart owner identifiers are resolved by performing an email match lookup against the Pipedrive Users API endpoint. Owners with a direct email match receive their corresponding Pipedrive User ID assignment. Unmatched owners are flagged in the migration report and require a fallback Pipedrive user to be specified prior to migration execution.

Call activity records from Pure Chart are created as Pipedrive Activity objects with the Type field set to 'call'. FlitStack preserves the original call date, call duration when available in the source data, and the assigned Person or Deal association for each migrated call record.

Email activities migrate from Pure Chart as Pipedrive Activity objects with Type='email'. The email subject line maps directly to the Activity subject field, while the email body maps to the content field when supported by the target Pipedrive plan tier configuration.

Meeting records from Pure Chart become Pipedrive Activity objects with Type='meeting'. Start time, end time, location details, and any Person or Deal associations are all preserved during the migration to maintain complete meeting context in the target system.

Note entries in Pure Chart are mapped to Pipedrive Activity objects with Type='task'. The note content maps to either the activity subject line or the body field depending on how Pure Chart structures its note field, ensuring the information remains searchable and accessible after migration.

Product catalog items from Pure Chart migrate to Pipedrive Products with a direct field mapping approach. Each Product retains its name, product code derived from the item_id, and associated pricing fields. Deals can reference these Products through deal_product entries to maintain accurate revenue tracking.

Custom contact fields defined in Pure Chart require pre-creation in Pipedrive through the POST /personFields API endpoint before data insertion can occur. Pipedrive returns a unique hash key for each custom field, which FlitStack stores in the field mapping configuration for value substitution during the migration data processing phase.

Custom deal-level fields in Pure Chart map to Pipedrive Deal custom fields through the POST /dealFields API endpoint. Fields that vary based on deal stage require creation as custom fields on the Deal object itself rather than at the stage level to ensure proper data association throughout the pipeline.

When Pure Chart contains Lead objects, they map directly to Pipedrive Leads which are available on Advanced and higher plan tiers. Leads inherit all standard Person fields and add lead-specific status fields such as lead value, source attribution, and qualification stage that are unique to the Lead object structure.

Workflow definitions configured in Pure Chart do not have a direct equivalent in Pipedrive and cannot be migrated automatically. FlitStack exports the complete workflow definitions as a reference JSON file that your Pipedrive administrator can review and use as a blueprint to rebuild equivalent automations in Pipedrive's Automation builder interface.