Migrate from LocaliQ to Twenty CRM

Dash Leads with AI-scored attributes, lifecycle stages, and engagement timestamps map to Twenty's Person object. The Dash lead score value, source channel (Voice, SMS, chat, web form), and first_contact_timestamp are preserved as custom fields on the Person record. We map dash_lead_status to Twenty's opportunity status field if the lead has an associated opportunity record, or store as a static custom field for segmentation. Dash multi-channel agent routing configurations are documented but not migrated as active routing rules.

LocaliQ Contacts with associated company references and custom fields map to Twenty Person records with the company linked via a lookup relationship. Any Dash-specific AI attributes attached to the Contact (beyond standard name/email/phone) are stored as custom fields created via the Twenty /metadata API before migration. Contact records without a company association map to Person standalone.

LocaliQ Company records map directly to Twenty Company. The company name, domain, address, and any custom properties migrate as standard and custom fields on the Company record. We resolve the company-contact relationship graph during import by inserting Company records first, then linking Person records via the companyId lookup.

Dash pipeline stages (lead qualification, proposal, negotiation, closed-won, closed-lost) map to Twenty Opportunity stages. We create the stage definitions in Twenty before migration, preserving the original stage names and ordering. Custom stages added in LocaliQ are inventoried and recreated as Twenty Opportunity stages with customer-confirmed labels.

LocaliQ supports custom properties on leads, contacts, and companies. We inventory every custom field, capture its data type, and create matching custom fields in Twenty via the /metadata API before data import. Multi-select and checkbox fields in LocaliQ map to Twenty multi-select picklists; date fields map to Twenty date fields; numeric fields map to number fields with appropriate precision.

LocaliQ marketing campaign metadata (name, status, budget allocation, channel) migrates as a custom Campaign object in Twenty. We preserve campaign name, status (active, paused, completed), and budget amounts. Campaign performance metrics (impressions, clicks, conversions) are sourced from connected ad platforms directly and are not pulled from LocaliQ's reporting layer during migration.

Dash AI agent configurations including greeting scripts, routing rules, and SMS templates are documented as configuration records in the migration inventory. We export the agent definitions to a JSON reference file and advise rebuilding equivalent routing and automation logic in Twenty using workflow rules or a third-party communication integration. Agent configurations do not migrate as active rules.

Automation sequences and trigger conditions in LocaliQ are documented in a written inventory delivered to the customer at migration close. Each workflow is described with its trigger, conditions, actions, and recommended Twenty equivalent. The customer's admin rebuilds automations in Twenty post-migration; this is out of standard migration scope.

Directory citation data across 100+ platforms migrates as read-only Listing records in a custom object, preserving listing URL, verification status, and directory name. The syndication mechanism does not transfer; listings must be re-verified at the destination directory directly. This is a data preservation step, not an active listings management capability.

Review data including ratings, content, dates, and response history from the LocaliQ dashboard migrates as read-only Review records in a custom object. Pending response drafts are preserved. Review management features (publishing, responding) require rebuilding at the destination platform or using a third-party reviews management tool.

References to connected Google Ads and Yelp Ads accounts are documented with connection metadata (account ID, platform, last sync date). We advise re-authenticating ad integrations directly in Twenty or a connected analytics platform post-migration. Ad performance data is not migrated as LocaliQ acts as a pass-through to the ad platforms themselves.

File attachments associated with leads or contacts are not accessible via the LocaliQ API. We advise exporting files manually from the LocaliQ dashboard prior to migration cutoff. If files are exported, they can be re-uploaded to Twenty as linked ContentDocument records post-migration.