Migrate from Paradym to Pipedrive

Paradym contact records map directly to Pipedrive People, preserving the primary email as the Person's email field. The Paradym owner ID is resolved by matching the owner's email address to an existing Pipedrive user, and that matched Pipedrive user becomes the owner assigned to the Person record in the destination system.

Paradym's nested person object contains structured name sub-fields that FlitStack splits into Pipedrive's separate first_name and last_name fields. If Paradym stores the contact name as a single full_name string instead of discrete components, FlitStack splits the string on the first encountered space character to populate the two Pipedrive name fields.

Paradym's nested address object with street, city, state, postal_code, and country cannot map directly into Pipedrive's single flat address field. FlitStack creates Pipedrive custom text fields (Address_Street__c, Address_City__c, Address_State__c, Address_Postal_Code__c, Address_Country__c) and populates each from the corresponding nested element. Alternatively, if a single address field is preferred, address components are concatenated into a single text string.

Paradym stores nationality as a nested array supporting multiple nationalities per person. Since Pipedrive has no native multi-value field type for arrays, FlitStack joins the array elements into a pipe-delimited string (e.g., 'US|UK|Canada') stored in a custom text field named Nationalities__c, preserving the complete list in a readable, searchable format.

Paradym company records map directly to Pipedrive Organizations. The company name maps to the Organization name field, and the website URL maps to the Organization web field. If the company record includes a nested address object, that address is mapped using the same custom-field flattening approach applied to person addresses.

When Paradym stores parent-child relationships between companies, FlitStack maps the parent company reference to Pipedrive's parent_id field on the Organization record. The parent Organization must be migrated and created in Pipedrive before any child companies are imported, ensuring the lookup reference resolves correctly during the migration run.

Paradym deals map directly to Pipedrive Deals with the deal name populating the Deal title field and deal value mapping to the Deal value field. The Paradym deal owner is resolved by matching the owner's email address to a Pipedrive user, who is then assigned as the deal owner in Pipedrive upon migration.

Paradym deal stages are arbitrary string values defined per account that must map to Pipedrive stage names within the target pipeline. FlitStack creates any missing Pipedrive stages before the migration runs and optionally maps probability percentages and forecast category values per stage for accurate pipeline reporting.

If Paradym exposes pipelines as named groupings of stages, these map directly to Pipedrive Pipeline objects. FlitStack first creates the Pipedrive pipeline structure including all stage definitions, then populates deals within those pipelines. Multiple Paradym pipelines correspond to multiple Pipedrive pipelines in the destination account.

Paradym engagement records including calls, emails, and notes map to Pipedrive Activities. The activity type is derived from the Paradym engagement type field, and the related Person or Deal is linked via Pipedrive's activity entity_id and entity_type foreign keys. Original creation timestamps from Paradym are preserved on the activity record in Pipedrive.

Paradym notes attached to contacts or companies map to Pipedrive Notes, linked to the corresponding Person or Organization record. Rich-text formatting is preserved where Paradym's API exposes it as HTML. If notes contain file attachments, those files are downloaded and re-uploaded to Pipedrive's file storage.

Paradym user and owner records map to Pipedrive Users by email address match. All contacts, companies, and deals owned by a Paradym user are assigned to the matched Pipedrive user after migration. If no Pipedrive user matches, the record is assigned to the migration admin and flagged for reassignment.

Paradym credential records and template definitions have no native equivalent in Pipedrive's CRM model. FlitStack migrates credential ID, issue date, expiry date, and issuer as custom fields on the Person record for audit and reference purposes. Credential logic and verification workflows must be rebuilt outside Pipedrive.

Files attached to Paradym contacts, companies, or deals are downloaded via the Paradym API, then uploaded to Pipedrive's file storage and linked to the corresponding Person, Organization, or Deal record using Pipedrive's file association API. Pipedrive's file size limit of 25MB per file applies to all imported attachments.

The Paradym internal record ID is stored as a custom text field called Source_System_ID__c on each migrated record in Pipedrive. This field enables accurate delta-run de-duplication, maintains audit traceability throughout the migration lifecycle, and supports post-go-live reconciliation checks against the Paradym source system.