Migrate from BlinQ to Twenty CRM

Blinq card-holder profiles map directly to Twenty People records with field-for-field translation. First name, last name, email, phone, job title, and address fields migrate directly. Blinq's card-sharing metadata (shares, views) and tag data are preserved in custom fields on the People record to maintain lead-scoring context and segmentation capability in Twenty's environment.

Blinq stores associated company names and domains on card profiles. These map to Twenty Companies records. The Blinq domain field maps to the Twenty Website field. Companies are migrated first so People records can reference them via companyId during import.

Blinq allows multiple associated companies per contact (N:N model). Twenty People records support a single primary companyId relation. FlitStack resolves the primary company using the most-recently-associated company or a specified priority rule, then surfaces additional associations as a custom field for reference.

Blinq tags and qualifiers (e.g., 'Event Attendee', 'Warm Lead', 'VIP') have no native equivalent in Twenty. We create a custom multi-select or text field (Tags__c) on the People object and populate it with the Blinq tag list, preserving the original taxonomy for filtering and segmentation.

Blinq meeting records with titles, dates, and notes map to Twenty Notes objects. Each Note is linked to the corresponding People record via the Note's relation field. Original meeting dates and titles are preserved as Note metadata fields so activity timelines remain accurate after migration.

Blinq tracks how many times two contacts have met or interacted. Twenty has no native meeting-count field. We migrate this as a custom integer field (Meetings_Count__c) on the People object, giving sales reps the same relationship-depth signal they had in Blinq.

Blinq card profiles include social media URLs (LinkedIn, Twitter, Instagram) as card fields. Twenty's People object has a standard Links field. For additional social links beyond the standard slots, we create custom URL fields (LinkedIn_URL__c, Twitter_URL__c) on the People object.

Blinq tracks how many times a card has been shared or viewed. These are engagement signals that sales teams used to prioritize warm leads. We migrate these as custom integer fields (Card_Shares__c, Card_Views__c) on the People object for reporting continuity in Twenty.

Blinq stores metadata about which external CRM a contact synced to and when. If Blinq contacts were previously synced to Salesforce or HubSpot, we preserve that sync history as a custom text field (CRM_Sync_History__c) on the People record so teams know which contacts were already enriched.

Blinq has no native workflow or automation engine. All automation lives in Zapier or similar third-party tools connecting Blinq to other CRMs. These integrations must be rebuilt as Twenty webhook triggers and Zapier/Make connections using Twenty's API. No Blinq-native automation data needs migration.

Blinq's credit-based billing (shares, scans, sync counts) is a platform-level billing construct with no equivalent in Twenty. We preserve remaining share credits and sync counts as a custom field (Blinq_Usage_Reference__c) for billing reconciliation purposes, but Twenty does not use this data for any platform feature.

Blinq Business and Enterprise plans allow custom card fields beyond the standard set. Each unique custom card field Blinq has configured becomes a custom field in Twenty's Settings → Data Model under the People object, with the field type matched to the data (text, URL, date, etc.).