Migrate from BlinQ to Pipedrive

Blinq Person records map directly to Pipedrive People using a one-to-one relationship. Standard fields including name, email address, phone number, job title, website URL, and physical address fields carry over as-is without transformation. The Person record must be created in Pipedrive before any linked Activities or custom field data can be attached to maintain referential integrity.

Blinq stores company information as a free-text field on each Person record rather than as a separate object. Our migration process extracts all unique company names, deduplicates them across all Person records, and creates corresponding Organization records in Pipedrive as a prerequisite step. Once Organizations exist, each Person record links to their appropriate Organization via the org_id foreign key relationship.

Blinq tags are flat string values stored as an array per person with no hierarchical structure. Since Pipedrive has no native tags object, we create a Pipedrive custom drop-down field and populate it with the Blinq tag value for each person during migration. When a person has multiple tags from different categories such as industry tags and event tags, we create separate custom fields per tag category.

Blinq Properties are custom key-value pairs stored per Person record through the Properties API, with key names that vary by account. These map directly to Pipedrive custom fields on the Person object. We call the Pipedrive /personFields endpoint to create each field using the Blinq Property key as the field label, then map the corresponding value per record during migration.

Blinq meeting notes are captured when business cards are shared at events and trade shows. These migrate as Pipedrive Activities of type 'meeting'. The Blinq note text becomes the Activity subject line, and the original timestamp from Blinq becomes the due date on the Pipedrive Activity. Event venue and attendee context are preserved in custom fields since Pipedrive Activities do not natively store event metadata like venue location or attendee names.

When a Blinq user shares their digital business card with a contact, Blinq records this as a timestamped event in the system. We translate each share event into a Pipedrive Activity of type 'note' attached to the Person record. This preserves the historical record of when the connection was first established, maintaining the relationship context in Pipedrive's activity timeline.

Blinq stores social profile URLs including LinkedIn, Twitter, Facebook, and other platforms as part of each person record. Pipedrive does not include native social URL fields on the Person object. To preserve this data, we create one custom text field per social platform and migrate the corresponding URL from Blinq into the appropriate Pipedrive custom field.

Blinq records the exact datetime when each person was first added to the system. Pipedrive Person records automatically receive a CreatedDate timestamp at migration time, which reflects when the record was created in Pipedrive rather than when the contact was originally added in Blinq. We preserve the original Blinq connection date as a custom datetime field on the Person record for reporting continuity and historical accuracy.

Blinq tracks how each person was captured in the system, recording attribution data such as QR code scan, email share, direct card exchange, CRM synchronization, or manual entry. This attribution string migrates as a custom drop-down field on the Pipedrive Person record, ensuring your team retains visibility into where each contact originated for segmentation and source analysis purposes.

Each Blinq contact record includes a unique blinq.me URL that points directly to that person's digital business card. We store this URL as a custom URL field on the Pipedrive Person record, providing quick reference access to the original Blinq card during and after the transition period for verification and back-reference purposes.