Migrate from Promio to Twenty CRM

Promio Leads map to Twenty Person records. We extract source attribution fields (campaign name, UTM parameters, referrer), call-tracking metadata (call duration, disposition, recording URL as text reference), and any custom properties discovered in the exported CSV headers. The original lead capture date migrates as a custom date field on the Person record because Twenty's standard Person object does not include a native source date field. Owner assignment maps from Promio's assigned user to Twenty's workspace Member via email match.

Promio's Customers object conflates contact and organization into a single record type. We split on the presence of company-level fields: records with a company name and domain map to Twenty Company records with the Person record linked via a work email; records without company context map directly to Person. Promio's lifecycle segmentation labels (New, Active, At-Risk, Lapsed, Lost) migrate as a custom select field on Person. This split requires a data quality review during scoping because Promio's export does not enforce a company-name field on all customer records.

Promio Campaigns map to Twenty Opportunity records to preserve the advertising context of the customer journey. Campaign name becomes the Opportunity name; associated ad budget and performance metrics (impressions, clicks, cost, conversions) migrate as custom numeric fields on the Opportunity. We link the Opportunity to the associated Person and Company records via Twenty's Opportunity object relationships. Note that Promio's Campaign bundles advertising channels (Google, Bing, Display) with drip sequences — the sequence logic does not migrate and is documented as an automation rebuild requirement.

Google Ads and Bing Ads account credentials linked through Promio are stored externally at the ad network level and are not portable via CRM migration. We extract the campaign structure, budget allocations, and performance history as a CSV artifact that the customer uses to re-onboard ad accounts directly in Google Ads and Bing. We attach a summary Note record to the relevant Company or Person in Twenty documenting the original campaign structure for reference.

Call recordings are hosted on Promio's infrastructure and are not included in CSV exports. We flag this as a hard-stop pre-flight item: the customer must download all required call recordings directly from Promio's interface before the migration cutover date. We cannot migrate these post-cutover. The recording URL reference in the exported call-tracking metadata is preserved as a text field on the Person record for audit traceability, but the audio file itself must be downloaded and hosted independently.

Promio landing pages are served from promio.com subdomains and are not exportable as portable HTML or redirect-configurable assets. We inventory all active landing pages during scoping — recording URL, form fields, and campaign association — and deliver a page-by-page rebuild requirements list as a migration artifact. The customer's web team or a developer uses this checklist to recreate pages in Twenty or on the customer's own domain.

Review monitoring data (aggregated ratings, review site URLs, reputation scores) is pulled from third-party aggregators into Promio's dashboard. We extract this as a set of custom fields on the Person record in Twenty: overall_rating (number), review_count (number), primary_review_url (url), and review_site (text). We do not migrate review content itself; the URL reference allows a sales rep to open the review in a browser.

Promio allows custom fields on Leads and Customers tied to its campaign attribution system. These are discovered during the extraction phase by inspecting exported CSV headers. We map each Promio custom property to a Twenty custom field on the appropriate standard object (Person or Company), using Twenty's supported field types (text, number, date, select, multi-select). Fields that represent a related entity (e.g., a reference to a campaign or external system) are mapped to a Twenty Custom Object with a lookup relationship if the data model warrants it.

Promio's assigned user on Lead and Customer records maps to a Twenty workspace Member. We resolve by email match against the Twenty workspace user list provisioned before migration. Any Promio Owner without a matching Twenty Member is held in a reconciliation queue for the customer's admin to provision before record import begins. Note that Twenty's Member model is scoped per workspace and includes role-based permissions that the customer's admin configures post-migration.

Promio's lifecycle labels (New, Active, At-Risk, Lapsed, Lost) are custom properties in Promio's schema. We map these as a custom select field lifecycle_segment__c on the Person object in Twenty with the same label values. This preserves the segmentation intelligence the customer has built in Promio and allows the customer's admin to use these labels in Twenty's filtering and grouping views without rebuilding the classification logic.