Migrate from Promio to Pipedrive

Promio Leads with source attribution, call-tracking metadata (call duration, disposition, recording link if available), and campaign source data migrate to Pipedrive Person records. Promio Leads with no associated Deal migrate as Pipedrive Lead inbox records. We resolve the split by checking whether a Promio Lead has a linked Campaign with closed revenue; if so it maps to a Person with an Organization link; if not it maps as a pre-deal Lead in Pipedrive's Lead Inbox.

Promio Customer records map to Pipedrive Person records with a lookup to a corresponding Organization (created from Promio's company-level data or inferred from the Customer's email domain). The primary lookup is satisfied before Person import begins to avoid orphaned records. Promio lifecycle segmentation labels (New, Active, At-Risk, Lapsed, Lost) migrate as a custom picklist field lifecycle_stage__c on the Person record for post-migration segmentation and reporting.

Promio classifies Customers into lifecycle segments as custom properties tied to its attribution layer. We preserve these labels as a Pipedrive custom picklist field on Person with values New, Active, At-Risk, Lapsed, and Lost. The custom field is created in Pipedrive before any Person import begins. Teams use this field to segment Pipedrive reporting views and automation triggers without losing the intelligence embedded in Promio's segmentation model.

Promio campaigns bundle advertising channels (Google, Bing, Display) with budget allocations and performance metrics tied to revenue outcomes. Pipedrive has no native campaign attribution object. We map campaign name, channel, associated budget, and key performance metrics (impressions, clicks, conversions, attributed revenue) as custom fields on the associated Pipedrive Deal record. This preserves the Promio attribution context in the CRM without requiring a separate marketing analytics platform to retain the data.

Promio stores call audio files on its own hosting infrastructure. These files are not included in CSV exports and cannot be retrieved via API. We flag this as a migration hard stop: customers must download all required call recordings directly from Promio's interface before the cutover date. We cannot migrate these post-cutover. We include this item in the pre-flight checklist that the customer's admin signs off on before we begin data import into Pipedrive.

Google Ads and Bing Ads account credentials and budget allocations are linked to Promio through its managed-service credential layer but stored at the ad network level. These credentials do not transfer with CSV exports and cannot be migrated into Pipedrive's CRM. We document the current campaign structure, budget allocations, audience segments, and performance history during the extraction phase. The customer independently re-grants ad account access outside of Promio and rebuilds campaign structures directly in Google Ads and Bing after migration.

Promio generates custom landing pages served from promio.com subdomains. These are not exportable as HTML, portable redirect configurations, or form definitions. We inventory all active Promio landing pages during the extraction phase, capturing URL, form field names, and traffic volume estimates from any available reporting. The customer receives a page-by-page rebuild requirements list as a migration artifact. Rebuild options include Pipedrive Web Forms (for form capture), the customer's own CMS, or a dedicated landing page platform.

Promio aggregates review monitoring data from third-party sites (Google, Yelp, Facebook ratings) into its dashboard. We extract the aggregated star rating, total review count, and review site URLs as custom fields on the corresponding Pipedrive Person record: reputation_rating__c (number), reputation_review_count__c (integer), and reputation_source_urls__c (text). These fields populate Pipedrive's contact detail view and are available for filtering in list views and reports.

Promio allows custom fields on Leads and Customers tied to its campaign attribution and lifecycle systems. We inspect exported CSV headers to discover all Promio custom property names and data types, then create equivalent Pipedrive custom fields (text, number, date, picklist, or boolean) on the Person and Deal objects before import. Custom fields added after the export date are not captured; we schedule the final export as close to the cutover date as possible and recommend a second export if the migration window exceeds 30 days.

Promio Owner records (sales reps and managers assigned to Leads and Customers) map to Pipedrive User records resolved by email address match. Owners without a matching Pipedrive User go to a reconciliation queue for the customer's admin to provision before record import resumes. This step is a gate on the Person and Deal import phases because OwnerId is a required reference on most standard Pipedrive objects.