Migrate from BlinQ to HighLevel

Blinq contact profiles map directly to HighLevel Contacts. Every Blinq field — name, email, phone, company, job title, and social links — maps to the corresponding HighLevel Contact field. Tags migrate as HighLevel Tags. Original scan timestamps are preserved as a custom datetime field (Blinq_Scan_Date__c) on the Contact record.

Blinq stores company name as a text property on the contact profile. FlitStack first checks whether a matching HighLevel Company record exists by domain or name; if not, it creates one and links the Contact via AccountId lookup. This ensures HighLevel's Company object is populated for reporting and Contact-to-Company association.

Blinq tags — such as event names, relationship qualifiers, booth numbers, lead tier indicators, and source channels — map directly to HighLevel Tags. Tags are assigned to contacts via HighLevel's tag management API after contacts are created. Duplicate tag names across the full Blinq dataset are identified and deduplicated during import to prevent unwanted tag proliferation in HighLevel.

Blinq AI conversation notes attached to a scanned contact do not map to a standard HighLevel object. FlitStack creates a long-text custom field (Conversation_Notes__c) on the HighLevel Contact record and populates it with the Blinq note content. If HighLevel's built-in Notes object is preferred, notes can alternatively be imported as separate Note records linked by ContactId.

Blinq records the exact timestamp when a card is scanned or a profile is shared. HighLevel has no native equivalent. FlitStack maps this to a custom datetime field (Blinq_Scan_Date__c) on the Contact, preserving the original date for segmentation and reporting continuity.

Blinq profiles store LinkedIn URL, Twitter/X handle, Instagram, Facebook, and any additional social fields configured by the admin. HighLevel Contact standard fields do not include social link storage. Each social platform maps to a named custom text field (LinkedIn_URL__c, Twitter_Handle__c, Instagram_Handle__c, Facebook_URL__c) on the Contact object for complete social identity preservation.

Blinq tracks the acquisition method for each contact — whether added via QR code scan, NFC tap, email share, or direct link. This metadata field has no equivalent in HighLevel's standard Contact model. FlitStack preserves it as a text custom field (Blinq_Share_Method__c) on the Contact record for segmentation, reporting, and analytics reference on how contacts entered the system.

Blinq Business plan assigns a card owner (typically the account holder or admin who provisioned the card). HighLevel users are matched by email address. Unmatched owners are flagged before migration — your team either creates a HighLevel user for them or assigns their records to a fallback user.

Blinq Business plan allows custom card fields beyond the standard set — custom text fields, pick-lists, or data fields created by the admin. Each custom Blinq field maps to a corresponding custom field on HighLevel Contact, using the same field type (text, pick-list, date, number) where supported.

Blinq's email signature builder is a destination-side feature within Blinq's platform. It cannot be exported and has no equivalent in HighLevel's data model. If your team uses Blinq email signatures, this configuration must be rebuilt manually or via HighLevel's email signature tools.

Blinq's Zapier-based CRM sync configurations — webhooks, trigger filters, and field mappings — are integration-level settings stored in Zapier, not in Blinq's data export. These must be recreated as new Zapier Zaps or HighLevel Workflow triggers pointing to the migrated HighLevel contacts.