Migrate from LocaliQ to Nutshell

LocaliQ Dash Leads with AI-scored attributes, engagement timestamps, and lifecycle stages map to Nutshell People records. The Dash AI lead score migrates to a Nutshell custom numeric field dash_lead_score__c so the sales team can prioritize the same records in Nutshell. We preserve Dash lifecycle stage as a custom text field dash_lifecycle_stage__c. HubSpot owner email is resolved to a matching Nutshell user; unresolved owners go to a reconciliation queue for the customer's admin to provision before record import.

LocaliQ Marketing Contacts with associated company references and custom fields map to Nutshell People. Any LocaliQ contact that is already a Dash Lead receives the People record with both dash_lead_score__c and marketing contact attributes preserved. Standard fields (name, email, phone, address) map directly; custom fields are created in Nutshell as custom fields before migration and mapped individually.

LocaliQ business accounts linked to contacts and campaign associations map to Nutshell Company records. The LocaliQ company name becomes the Nutshell Company name; domain, address, and industry fields map to Nutshell's corresponding Company fields. The company-contact relationship graph is preserved at migration time by inserting Companies before People so that Nutshell's Company-Person link is satisfied at insert.

LocaliQ Dash pipeline stages tracking lead progression map to Nutshell Deal pipeline stages. We inventory every stage name, ordering, and probability percentage from LocaliQ and configure matching Nutshell pipeline stages before migration. If LocaliQ stages use custom names not present in the default Nutshell pipeline, we create new stage values in the Nutshell pipeline configuration during the setup phase.

LocaliQ supports custom properties on leads, contacts, and companies. We inventory all active custom fields, their data types, and populated values during scoping. Custom fields are pre-created in Nutshell with matching types (text, number, date, dropdown) before any record import begins. Any LocaliQ custom field that has no equivalent Nutshell type is documented with its values for the customer to review and reclassify during setup.

LocaliQ marketing campaigns across search, social, and display channels export as campaign metadata (name, budget, status, dates). Nutshell does not have a native Campaign object, so campaign associations are preserved as Activity notes on the related Person or Company record or as tags that can be reviewed by the sales team post-migration. Performance metrics (impressions, spend, leads generated) are documented as a separate reference spreadsheet for manual re-entry into Nutshell's reporting.

LocaliQ review data including rating, content, date, and response history is exported as a structured record. Because Nutshell does not have a native Reviews object, we attach review data as Activity notes on the related Nutshell Company record with a tag prefix review_ so the sales team can locate and review the content. Response drafts from LocaliQ are preserved as Note records. The review-response history requires manual review and re-posting at the destination platform if the customer maintains a review management workflow.

LocaliQ directory citation data across 100+ platforms is exported as listing details, verification status, and citation URLs. Nutshell has no native listings object, so we attach listing data as Notes on the associated Nutshell Company record with a tag prefix listing_. The syndication mechanism does not transfer—listings must be re-verified at each directory platform individually. We deliver a directory-by-directory verification checklist as part of the migration output.