Migrate from Promio to Zoho CRM

Promio Lead records map directly to Zoho CRM Leads. Source attribution fields (campaign name, utm parameters, referrer) from Promio migrate as custom text fields on the Zoho Lead. If the Promio Lead originated from a call-tracking number, the call-tracking phone number and disposition notes map to Zoho Lead custom fields. Lead conversion in Zoho creates a Contact and (optionally) an Account from the same Lead record. We preserve the original Promio lead ID in a custom field promio_lead_id__c for reconciliation.

Promio Customer records map to Zoho CRM Contacts. The Promio lifecycle stage (New, Active, At-Risk, Lapsed, Lost) migrates as a custom picklist field lifecycle_stage__c on the Contact. Address, email, phone, and primary contact fields map to standard Zoho Contact fields. We resolve any Company name in Promio's Customer record to a Zoho Account before Contact insert so that the Account Lookups are satisfied. If Promio stores a customer as both a Lead and a Customer, we deduplicate by email before inserting.

Promio Customers with a company name field map to Zoho CRM Accounts. Account Name maps directly; website, industry classification, and annual revenue migrate to standard Account fields. We create the Account before importing the related Contact so that the Account Lookup on Contact is satisfied at insert time. Multiple Promio Customers belonging to the same company domain map to a single Zoho Account with multiple Contact children.

Promio Campaigns (bundling advertising channels with drip sequences) map to Zoho CRM Campaigns. Campaign Name, Start Date, and End Date migrate directly. Promio's channel type (Google, Bing, Display) migrates as a custom picklist field campaign_channel__c. We do not migrate Promio's automated drip sequence logic as workflows; we document the sequence structure (stages, delays, actions) as a rebuild requirements artifact for the customer's admin to implement in Zoho Workflows or Blueprint post-migration.

Promio's campaign-level advertising metrics (impressions, clicks, spend, conversions, revenue-attributed) migrate as custom numeric fields on the Zoho CRM Campaign record. We inventory all metrics available in the Promio CSV export and create matching custom fields in Zoho before import. Metrics are snapshot values at export time; we do not migrate historical time-series performance data beyond the most recent values. Customers needing historical campaign analytics should retain the Promio export files.

Promio call-tracking records (not the recordings themselves) include phone number, call duration, disposition, recording URL reference, and timestamp. We extract these fields from the Promio CSV export and map them to custom fields on the Zoho Contact: call_last_date__c, call_last_duration_sec__c, call_disposition__c, and call_recording_url__c. The call_recording_url__c field contains a link back to Promio's infrastructure; the customer must download recordings before cutover. We cannot migrate audio files or update Promio-hosted URLs post-cutover.

Promio's custom properties on Lead records are discovered by inspecting the CSV header row during extraction. We create matching custom fields in Zoho CRM Lead module before import, matching the field type (text, number, date, picklist) as closely as possible given Zoho's field type options. Any picklist values from Promio are replicated as Zoho picklist options. Custom properties added in Promio after the export date are not captured; we schedule the final export as close to cutover as possible to minimize this gap.

Promio's custom properties on Customer records are discovered by inspecting the CSV header row. We create matching custom fields in Zoho CRM Contact module before import. If a Promio custom property stores a numeric score or rating, we map it to a Zoho numeric field; if it stores a label, we map it to a Zoho picklist or text field depending on cardinality. The Promio lifecycle stage property (New, Active, At-Risk, Lapsed, Lost) is a required custom field on Contact and is handled separately from other custom properties.

Promio aggregates review monitoring data (overall rating, review site URLs, reputation score) from third-party aggregators into its dashboard. We extract these values from the Promio CSV export and map them to custom fields on the Zoho Contact record: review_rating__c (numeric), review_site_url__c (URL), and reputation_score__c (numeric). We do not migrate the raw review text or review submission history as Zoho does not have a native reviews object.

Promio links Google Ads and Bing Ads accounts through its managed-service credential layer. These ad account credentials do not transfer on migration; the customer must independently re-grant access to their ad accounts in Google Ads and Bing directly. We inventory the current campaign structure, budget allocations, and audience settings from the Promio export and deliver a structured ad account re-onboarding checklist so the customer's marketing team can rebuild campaigns in Google Ads and Bing after migration. This object is flagged as out-of-scope for CRM data migration but included in the scope document as a post-migration action item.

Promio's call-tracking feature stores audio recordings on Promio's own hosting infrastructure. These files are not included in standard CSV exports and cannot be accessed via API. We flag this as a hard stop in the pre-flight checklist: customers must download all required call recordings directly from Promio's interface before the migration cutover date. We provide a checklist of Promio interface steps for downloading recordings and set a cutover date that gives the customer at least five business days to complete this download. We cannot migrate recordings post-cutover and do not provide storage for audio files.

Promio generates custom landing pages as part of its lead-capture stack, served from promio.com subdomains. These pages are not exportable as HTML or redirect-configurable assets. We inventory all active landing page URLs, form field labels, and lead destination mappings during scoping and deliver a page-by-page rebuild requirements list as a migration artifact. The customer's admin or web team rebuilds these pages in Zoho Forms, the customer's own website, or a third-party landing page tool post-migration.