Migrate from LocaliQ to Salesforce Sales Cloud

LocaliQ Leads from Dash carry AI-scored attributes (lead_score, lifecycle_stage, engagement_timestamps) that have no direct Salesforce equivalent. We split at migration time: unqualified Leads map to Salesforce Lead; Leads with confirmed contact information and purchasing intent map to Salesforce Contact attached to an Account. The original Dash AI score migrates to a custom field dash_lead_score__c on Lead; lifecycle stage becomes dash_lifecycle_stage__c. We flag any Dash leads with missing email addresses for manual enrichment before Salesforce import because Salesforce requires email format on Contacts.

LocaliQ marketing Contacts map to Salesforce Contact. We preserve the contact-company relationship graph using LocaliQ's company_reference field to resolve the AccountId lookup. Custom fields on LocaliQ contacts map to Salesforce custom fields with equivalent data types (text, number, date, picklist). Dash-specific AI attributes attached to Contact records are preserved in custom fields.

LocaliQ Company records map directly to Salesforce Account. Company name becomes Account Name; address fields map to BillingAddress fields. The company-contact relationship graph is preserved by resolving the AccountId on Contact records during import. Custom properties on the Company record map to Salesforce Account custom fields.

LocaliQ Campaigns map to Salesforce Campaign for marketing campaign tracking. Campaign budget and performance metrics that represent closed or won revenue are also mapped to Salesforce Opportunity records tied to the customer's Account, allowing pipeline reporting in Salesforce to reflect campaign-attributed deals. Campaign status (active, paused, closed) maps to Campaign Status field.

LocaliQ Dash pipeline stages (prospecting, qualified, proposal, negotiation, closed) map to Salesforce Opportunity Stage values. We configure the stage ordering and probability percentages in Salesforce before migration. Custom pipeline stages in LocaliQ become custom Opportunity Stage values in a Salesforce Sales Process configured per the customer's business process.

Dash AI agent configurations (greeting scripts, routing rules, SMS templates, operating hours) are exported as a structured configuration inventory document, not as migratable records. Salesforce does not have an equivalent native AI agent object; the customer uses this inventory to configure Salesforce Einstein Copilot, High Velocity Sales, or a third-party sales engagement tool. We do not migrate agent logic as executable code.

LocaliQ Dash workflows with triggers, conditions, delays, and CRM actions are documented as a written inventory with trigger type, conditions, actions, and recommended Salesforce Flow equivalent. Workflows do not migrate as executable code. The inventory is delivered to the customer's Salesforce admin for rebuild in Flow post-migration. Sequence cadences are documented separately with cadence step and timing information.

LocaliQ Review data (ratings, content, dates, response history) migrates as records in a Salesforce custom object (Review__c) or as Case records if Service Cloud is included. The migration approach is confirmed during scoping based on whether the customer wants review management to live inside Salesforce's service workflow or as a standalone reporting object. Pending response drafts migrate to the response field on the record.

Directory citation data across 100+ platforms migrates to a Salesforce custom object (Listing__c) with fields for directory name, listing URL, verification status, and citation consistency score. The syndication mechanism does not transfer; listings must be re-verified at the destination. We preserve the citation URL and verification status so the customer's admin can prioritize re-verification for high-value directories.

References to connected Google Ads and Yelp Ads accounts are documented as a connectivity inventory with account ID, platform, and last-sync timestamp. The actual ad account credentials and historical ad performance data remain in the ad platform and are not migrated to Salesforce. We document the re-authentication steps needed to connect ad platforms to Salesforce Campaign influence reporting or a revenue intelligence tool post-migration.

All LocaliQ custom properties on Lead, Contact, Company, and Campaign objects are inventoried during discovery with their data type, populated values, and usage frequency. Custom fields are pre-created in Salesforce before data import, with field types matched to Salesforce's supported types (Text, Number, Currency, Date, Picklist, Checkbox, etc.). Dash AI-specific attributes are prefixed with dash_ in the Salesforce API name.

LocaliQ engagement records (call logs, email activity, meeting records, task completions) migrate to Salesforce Task and Event objects. Calls map to Task with TaskSubtype=Call and CallDurationInSeconds in a custom field. Meetings map to Event with StartDateTime, EndDateTime, and Location preserved. Emails map to EmailMessage records linked to Tasks. The WhoId on Task/Event points to the resolved Lead or Contact; WhatId points to the related Account or Opportunity. We use Bulk API 2.0 with chunking for volumes over 50,000 records.

LocaliQ notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent Lead, Contact, Account, or Opportunity. File attachments associated with leads or contacts are not accessible via the LocaliQ API. We advise customers to export files manually from the LocaliQ dashboard prior to migration cutoff and provide a file inventory checklist to ensure nothing is missed.