Migrate from Plumb5 to Microsoft Dynamics 365 Sales

Plumb5 Customer Profiles map to Dynamics 365 Contact records, each associated with a parent Account (created from the Plumb5 Company entity if present, or provisioned as a standalone Account during migration). Standard fields including name, email, phone, and address migrate directly. Custom properties on the Plumb5 profile become custom fields on the Dynamics 365 Contact entity. We resolve AccountId lookups before Contact insert so the parent relationship is satisfied at the time of record creation.

Plumb5 marketing campaigns migrate to Dynamics 365 Marketing List (for audience membership) and Campaign (for goal and performance tracking). Campaign membership is preserved as Marketing List Member records linked to the migrated Contact records. Campaign goals and performance metrics from Plumb5 are documented as custom fields on the Campaign record for reporting reference. Plumb5 automation workflows tied to campaigns require rebuild in Power Automate or Microsoft Dynamics 365 Sales native workflows post-migration.

Plumb5 Deals map to Microsoft Dynamics 365 Sales Opportunity records. The Plumb5 deal value and deal stage migrate as custom fields on the Opportunity (plumb5_deal_value__c and plumb5_deal_stage__c) since Dynamics 365 stage definitions differ from Plumb5 pipeline stages. AccountId and ContactId lookups resolve from the parent Account and Contact records created in the profile migration phase. OwnerId resolves via email match against the Dynamics 365 User table.

Plumb5 behavioral events (web visits, email opens, form submissions, channel interactions) migrate to Microsoft Dynamics 365 Sales activity records. Event type maps to Activity type: email engagement to Email, web visits to custom Note records, channel interactions to Task. Timestamps and recency data migrate as Activity date fields and custom numeric fields on the Contact record (days_since_last_interaction__c). Event volume can be large, so we chunk writes via the Dataverse Bulk API with exponential backoff on throttling responses.

Plumb5 behavioral score values migrate as a read-only custom numeric field (plumb5_score__c) on each Contact record. The score definitions, point values, and rule logic are documented during discovery and delivered as a written inventory so the customer's Dynamics 365 team can rebuild equivalent scoring using Power Automate conditions, Sales AI, or a custom Power Apps canvas app. Active scoring rules cannot be migrated as executable configuration.

Plumb5 tags each customer interaction with a source channel (organic search, paid search, social, email, referral, direct). Channel attribution stored on the profile migrates as Dynamics 365 Topics applied via TopicAssignment records against the Contact, or as a custom multi-select picklist field (plumb5_channel_source__c) depending on the customer's reporting preference chosen during scoping.

Plumb5 defines a proprietary customer lifecycle from anonymous visitor through brand advocate. Microsoft Dynamics 365 Sales does not have a native equivalent lifecycle field. We map Plumb5 lifecycle values to the closest Dynamics 365 Contact attribute (for customers) or store as a custom picklist field (plumb5_lifecycle_stage__c) on the Contact. Stages with no direct Dynamics 365 equivalent are flagged in the migration documentation with a recommendation for post-migration naming alignment with the customer's sales process stages.

Plumb5 user-defined fields extending the standard profile schema are discovered during the schema audit phase and mapped to equivalent custom fields on the Dynamics 365 Contact or Account entity. Field data types are matched to Salesforce Field API types (text, number, date, picklist, boolean). Custom field names append the __c suffix per Dataverse naming convention and preserve the Plumb5 field label as a reference in the migration field map.