Migrate from Promio to Microsoft Dynamics 365 Sales

Promio Lead records with source attribution, call-tracking metadata, and campaign reference migrate to Microsoft Dynamics 365 Sales Lead. The Promio lead source field maps to LeadSource. Call duration and disposition data migrate to custom Lead fields we pre-create in the destination org. Any Promio Lead without sufficient qualification data (name, email, company) is flagged in the reconciliation report for the customer's admin to review before final import.

Promio Customers are person records (contacts) linked to a business entity. We split each Promio Customer into a Microsoft Dynamics 365 Sales Account (business) and Contact (person), using the Promio Customer's company association as the Account name. Lifecycle segmentation labels (New, Active, At-Risk, Lapsed, Lost) migrate as a custom multi-select picklist or text field on Contact so the customer retains segmentation intelligence. Customer-level reputation and review scores from Promio migrate as custom Contact fields linked to the review source URL.

Promio Campaigns (Google Ads, Bing Ads, Display) with associated ad budgets, performance metrics, and campaign structure migrate to Microsoft Dynamics 365 Sales Campaign. Campaign name and status map directly. Promio's bundled spend data migrates as custom numeric fields on Campaign (e.g., promio_budget_spent__c) since Microsoft Dynamics 365 Sales does not have a native ad spend field. We note that Microsoft Dynamics 365 Sales Campaign tracks marketing campaign effectiveness against CRM records but does not replace Google Ads or Bing Ads campaign management directly.

Promio's custom fields on Leads and Customers are not publicly documented; we discover them during the extraction phase by inspecting exported CSV headers. Each discovered custom property becomes a corresponding custom field on the appropriate Microsoft Dynamics 365 Sales object (Contact or Lead) with a type-mapped Salesforce field type. Field naming follows Promio's label converted to a valid API name with a promio_ prefix for traceability. Custom fields added after the initial export date require a second export run; we schedule the final export as close to cutover as possible.

Google Ads and Bing Ads account credentials linked through Promio's managed-service layer do not transfer automatically. We inventory the current campaign structure, budget allocations, performance history, and audience targeting from Promio exports and deliver a documented rebuild requirements list so the customer's team can re-grant ad account access and reconstruct campaigns in Google Ads and Bing directly. This is explicitly out of scope for CRM migration.

Promio aggregates review monitoring data from third-party sites (ratings, review site links, reputation scores) into its dashboard. We extract aggregated scores and review site URLs as custom fields on the corresponding Contact record in Microsoft Dynamics 365 Sales . No review site API integration migrates automatically; the customer configures any new reputation monitoring tool separately post-migration.

Promio stores call recording audio files on its own infrastructure and does not include them in standard CSV exports. We cannot migrate these. As a pre-flight checklist item, we instruct the customer to download all required call recordings directly from Promio's interface before the migration cutover date. Call recording links in Promio's data export are preserved as a text field on the Contact record for reference, but the audio files themselves must be downloaded and hosted independently.

Promio generates custom landing pages on promio.com subdomains; these are not exportable as HTML or redirect-configurable assets. We inventory all active landing pages during scoping, capture URL patterns, form field names, and submission targets, and deliver a page-by-page rebuild requirements list as a migration artifact. The customer's team rebuilds landing pages in Dynamics 365 portals, Power Apps, or their own website post-migration.