Migrate from BlinQ to Nutshell

Blinq contact profiles map directly to Nutshell People records. Standard fields including name, email, phone, and job title transfer as direct field mappings. Blinq custom card fields become Nutshell custom fields on the Person record, preserving any extended data your team captured. One Blinq contact profile results in one Nutshell Person record, maintaining a one-to-one relationship throughout the migration.

Blinq contacts may include an associated company name and website pulled from the card profile. These map to Nutshell Organizations using direct field mapping. When a Blinq contact has no company associated, we create a placeholder Organization or flag the record for manual association after migration completes, ensuring no contacts are orphaned during the transfer.

Blinq tags and qualifier labels have no native Nutshell equivalent, requiring a custom field approach. We create a Tag__c pick-list field on the Person object in Nutshell and populate each contact's tags as comma-separated pick-list selections. Teams can refine the tag taxonomy post-migration by editing the pick-list options in Nutshell Settings to match their evolving categorization needs.

Blinq star ratings on contacts transfer to a custom Number field called Rating__c on the Person object in Nutshell. If no rating exists on a Blinq contact, the field remains blank and is not populated. Ratings are preserved as integers from 1 to 5, maintaining the full fidelity of your contact prioritization data.

Blinq meeting notes and AI-generated conversation summaries are stored as Note records in Nutshell, with each note linked to the corresponding Person record. The content is extracted from Blinq's JSON response and written as plain-text Note body, preserving the full text of meeting discussions and AI conversation context for future reference by your team.

Blinq allows a contact to be associated with multiple cards or organizations simultaneously. In Nutshell, Contact Relationships link a Person to an Organization using a dedicated relationship object. When a Blinq contact maps to multiple organizations, we create one primary Contact Relationship in Nutshell and surface additional links for manual completion during the post-migration review phase.

Blinq card template name, branding theme, and visual layout have no structural equivalent in Nutshell's object model. We store the card template name as a Note on the Person record so the context is preserved for reference, but the design itself cannot be reproduced in Nutshell since it lacks card-design capabilities.

Blinq card owners (team members who created the card) are stored as a Source_Owner__c text field on the Nutshell Person record. Nutshell user matching is performed by email address where possible, allowing us to link Blinq owners to existing Nutshell users. Unmatched owners are flagged in a pre-migration report for your team to resolve before the full migration runs.

Blinq stores multiple phone numbers per contact including primary, mobile, and work numbers. The primary phone maps to the Person.Phone field in Nutshell. Secondary numbers including mobile and work phones map to Person.OtherPhone and Person.HomePhone fields. Dedicated organization-level phone numbers are stored as custom fields on the Organization record.

Blinq social profile URLs including LinkedIn and Twitter/X do not map to standard Nutshell Person fields. We create LinkedIn_URL__c and Twitter_URL__c text fields on the Person object in Nutshell to store these URLs. Instagram and other platform URLs are stored in a generic Social_URLs__c field as a comma-separated list for comprehensive social presence documentation.

Blinq card templates support custom text, number, date, and pick-list fields that extend beyond standard contact data. Each custom field in Blinq requires a corresponding custom field in Nutshell on either the Person or Organization object, depending on whether the field applies to the individual contact or their associated company. The field type is preserved during migration to maintain data integrity.

If the Blinq data includes contacts marked as leads or prospects without a sale, those records can be imported as Nutshell Leads rather than People. The migration plan determines the split based on contact status in Blinq before data extraction, ensuring leads enter your Nutshell pipeline in the correct state for follow-up by your sales team.

Blinq tracks how a contact was added including QR scan, card share, and manual import methods. This attribution data has no native Nutshell field for storing acquisition source. We attach the source information as a Note on the Person record for audit trail and analytics reference, preserving the full context of how each relationship began even though it cannot function as a filterable CRM field.

Blinq logs CRM sync events and timestamps for contacts that were previously connected to other CRMs. This sync audit trail is stored as a Note on the Nutshell Person record after migration. The note records the last Blinq sync timestamp and destination CRM name if applicable, preserving historical sync context for auditing purposes even though no native equivalent field exists in Nutshell.

Blinq manages email signature templates for team members as part of its outbound communication features. This is an outbound communication asset, not CRM contact data, so it does not belong in Nutshell's data model. Email signatures should be rebuilt using Nutshell's email settings or a dedicated email signature management tool after migration, preserving your team's professional communication branding independently.