Migrate from LocaliQ to Pipedrive

Dash leads are the primary migration object. We extract AI-scored attributes (lead score, lifecycle stage, engagement timestamps, source channel) and map them to Pipedrive Person custom fields. Dash lead properties that do not map to standard Pipedrive Person fields are preserved as custom fields, with data types matched to Pipedrive's supported field types (numeric for scores, date for timestamps, text for identifiers). Dash lifecycle stages are mapped to Pipedrive stage values or stored as a custom picklist field for reporting alignment.

LocaliQ marketing contacts with company associations and custom fields map to Pipedrive Person. Standard contact fields (name, email, phone, address) map to Pipedrive Person fields; any Dash-specific AI attributes attached to the contact record are added as custom fields. We preserve the contact-to-company relationship by resolving the LocaliQ company reference to a Pipedrive Organization record during import.

Business accounts from LocaliQ map to Pipedrive Organization. We preserve the company-contact relationship graph by creating Organizations before Person records and resolving the OrganizationId reference at Person insert time. Any custom properties on the LocaliQ company record migrate to Pipedrive Organization custom fields, with data type mapping applied to match Pipedrive's supported types.

Dash pipeline stages map to Pipedrive Deal stages. We inventory all LocaliQ pipeline stage names, ordering, and stage-level probabilities during scoping and replicate them as Pipedrive Deal stage values in the customer's pipeline configuration. Custom stage names are preserved verbatim; stage probability percentages are rounded to the nearest Pipedrive-supported integer value.

LocaliQ campaigns map to Pipedrive Deals for tracking budget and status, with associated Activities for campaign-related interactions. Campaign metadata (name, channel, budget allocation, status) becomes Deal custom fields; performance metrics are documented separately because they are sourced from connected ad platforms and cannot be replicated in Pipedrive without linking the ad integrations directly.

LocaliQ review data (ratings, content, dates, response history) migrates as Pipedrive Notes attached to the relevant Organization or Person record. We capture the full review text, star rating, source platform, and any pending response drafts. Review response history is preserved as a separate Note with a dated timestamp to maintain the conversation timeline.

All LocaliQ custom properties on leads, contacts, and companies are inventoried during scoping, with data types identified and mapped to Pipedrive field types (text, numeric, date, picklist, boolean). We pre-create all destination custom fields in Pipedrive before any data import so that the field exists at migration time. Custom field labels and API names are preserved where possible, with a __c suffix added per Pipedrive convention.

Directory citation data (listing URLs, verification status, citation platforms) is exported from LocaliQ and mapped to Organization custom fields or a separate custom object in Pipedrive. The syndication mechanism itself does not transfer—listings must be re-verified at the destination directories after migration. We document the current citation profile as a structured reference for the customer's admin to re-establish listing management in Pipedrive or a third-party tool.

AI agent configurations including greeting scripts, routing rules, and SMS templates are exported as a written configuration inventory rather than transferred as executable code. Pipedrive does not natively support AI agent functionality in the same manner as LocaliQ's Dash platform; the customer uses the configuration documentation to re-implement equivalent routing and automation logic in Pipedrive's workflow builder or a third-party conversational AI tool.

File attachments associated with leads, contacts, or companies are not accessible via the LocaliQ API. We advise customers to export files manually from the LocaliQ dashboard prior to migration cutoff and store them in a shared location for manual re-attachment in Pipedrive post-migration. This limitation is documented in the migration scope and flagged during discovery.