Migrate from Pipz to Microsoft Dynamics 365 Sales

Pipz Contacts map to Dynamics 365 Lead for unqualified records and Contact for qualified records under an Account. We apply a qualification rule during scoping based on lifecycle stage, pipeline association, and deal linkage to determine which records become Lead versus Contact. All Pipz contact fields (email, name, phone, custom properties) map to the equivalent typed fields in Dynamics 365. Pipz contacts without a linked Company map to standalone Leads; Pipz contacts with a linked Company map to Contacts under the migrated Account.

Pipz Company records map 1:1 to Dynamics 365 Account. The Company domain or website field becomes the Account Website. Account is created before any Contact import so the AccountId lookup is satisfied at the moment of Contact insert. Pipz's multi-contact-per-company relationship is preserved via the Contact.AccountId relationship in Dynamics 365.

Pipz Deals map to Dynamics 365 Opportunity. The Pipz deal stage maps to a Microsoft Dynamics 365 Sales Process stage via the Opportunity StageName field, with probabilities carried over from Pipz where stage-level probability percentages are configured. The Opportunity AccountId is resolved from the linked Pipz Company at migration time.

Each Pipz pipeline with its configured stages becomes a Microsoft Dynamics 365 Sales Process attached to an Opportunity Record Type. Stage names and order transfer directly. Pipz stage automation triggers (e.g., email sent when deal enters a stage) do not migrate; we document each trigger as a Power Automate rebuild recommendation in the automation inventory delivered post-migration.

Pipz Activities capture email opens, link clicks, chat conversations, page views, and automation-triggered events as timestamped records. We split by event type: email interactions map to Dynamics 365 EmailMessage records linked to Tasks; meeting-related events map to Event with StartDateTime and EndDateTime; all other events map to Task with a custom activity type field preserving the original Pipz event name. All timestamps transfer intact for full lifecycle reconstruction.

Pipz Email Campaigns (metadata, subject, send date, status, performance metrics) map to Dynamics 365 Campaign records. Campaign Member status (Sent, Delivered, Opened, Clicked) maps to CampaignMember Status values. The campaign linked contact list migrates as CampaignMember records linking the imported Contacts or Leads to the Campaign.

Pipz Smart Segments are built from demographic, tag-based, and behavioral rules. We extract the segment definition as a written saved-view filter specification (field, operator, value per rule line) and flag the segment for manual recreation in Dynamics 365 using Advanced Find saved views or Power Automate-triggered dynamic lists. Behavioral rule logic that cannot be expressed in Dynamics 365 filter syntax is documented separately.

Pipz tags are applied across contacts, companies, deals, and campaigns as flexible labels. We assess whether the tag scope maps better to a multi-select picklist on the relevant Dynamics 365 entity or to a Note record with a tag-category field. The customer chooses during scoping. We transfer all tag values and their record associations so that tag-based filtering is functional immediately after migration.

Custom fields on Pipz Contacts, Companies, and Deals map to typed custom attributes in Dynamics 365 (text, number, picklist, date, boolean, etc.). We extract the full field definition including data type, options list, and conditional visibility rules during scoping, then pre-create the destination schema in the customer's Dynamics 365 sandbox before any data loads. Validation rules and required-field constraints require admin coordination to temporarily bypass during import.

The Customer Engagement Index is Pipz-proprietary and has no native equivalent in Microsoft Dynamics 365 Sales . We extract the CEI raw value from each Pipz contact record and preserve it as a custom numeric field (cei_score__c) on the Dynamics 365 Contact entity. The customer can use this field for reporting, segmentation, or as a baseline for Microsoft Dynamics 365 Sales Insights scoring if they license the Premium tier. We do not replicate the CEI algorithm; we transfer the last known score only.

Pipz Users are assigned as owners to contacts, deals, and automation flows. We extract every distinct Pipz user referenced as an owner and match by email against the destination Dynamics 365 User table. Users without a matching Dynamics 365 User record are held in a reconciliation queue for the customer's admin to provision before record import resumes. Pipz includes deactivated users in exports; we filter to active owners unless the customer requests otherwise.