Migrate from Perfectview to Microsoft Dynamics 365 Sales

Each Perfectview Relation maps to one Account record in Microsoft Dynamics 365 Sales . The company-level fields from the Relation (company name, address, phone, website, industry) become the Account fields. We use RelationName as Account Name and the primary business address fields as BillingAddress. Account is created before any Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert. Relations without a distinguishable company component (individual-only records) skip Account creation and go directly to Contact with no Account link.

Each role-address instance within a Relation (for example, a Relation with both a billing contact and a sales contact) generates a separate Contact record linked to the parent Account. We use the Role field on the Relation address to set Contact Title and Department. The primary email and phone fields from the Relation become Contact Email and Phone. If a Relation has only one Contact role, we create one Contact; if it has five roles, we create five Contact records. The original Relation ID is preserved in a custom field pv_relation_id__c for audit trail and future delta-sync.

Perfectview Leads that are not yet converted to Relations map directly to Microsoft Dynamics 365 Sales Lead. We use LeadSource to capture the original lead acquisition channel and preserve any Perfectview lead score in a custom field pv_lead_score__c. Lead conversion during migration is handled by the customer's admin post-migration rather than as part of the bulk import to avoid creating duplicate Accounts.

Perfectview Deals map to Microsoft Dynamics 365 Sales Opportunity. The Deal amount, stage, close date, and owner migrate to Opportunity Amount, StageName, CloseDate, and OwnerId respectively. We map Perfectview's dealstage values to a Salesforce-compatible stage name set defined during scoping. The Opportunity AccountId is resolved by matching the parent Relation's company fields to the newly created Account record.

Perfectview Activities (calls, emails, meetings, tasks) migrate as Microsoft Dynamics 365 Sales Task and Event records. Call dispositions and durations map to custom Task fields; meeting start and end times map to Event StartDateTime and EndDateTime. Each Activity is linked to the parent Contact or Account via the Regarding (regardingobjectid) lookup. We use the Bulk API 2.0 for Activity migration because the record volume typically exceeds what the Dynamics 365 REST API can handle without batching.

Perfectview Cases migrate to Microsoft Dynamics 365 Sales Case with Status, Priority, Description, and Case Origin preserved. The Case Contact and Case Account are resolved by matching the original linked Relation to the newly created Account and Contact records. Case comments and conversation history migrate as EmailMessage records linked to the Case. If the Dynamics 365 tenant does not include Service Cloud, Cases are migrated as custom records in a custom object with equivalent fields.

Perfectview Document metadata (filename, file type, upload date, author) migrates to Dynamics 365 SharePoint integration document locations or to Salesforce ContentDocument records if the tenant uses Dataverse file attachments. The document binary files are exported from Perfectview via the bulk export function or API download endpoint, then re-uploaded to the equivalent SharePoint document library or ContentVersion record. The mapping between the original document ID and the new location ID is preserved in the migration mapping file.

Perfectview Quotes migrate to Microsoft Dynamics 365 Sales Quote. Quote headers (quotenumber, account, contact, validity period) map to Quote fields. Line items map to QuoteLineItem records, with Product2 and PricebookEntry resolved at migration time. Signed Quote PDFs migrate as ContentDocument attached to the Quote. Quote status (Draft, Active, Revised, Accepted, Closed) maps to the Dynamics 365 Quote Status field.

Perfectview Owners map to Dynamics 365 User records by email match. We resolve each Owner referenced on Relation, Deal, Activity, Case, and Quote to a Dynamics 365 User. Any Owner without a matching Dynamics 365 User is held in a reconciliation queue for the customer's admin to provision before the relevant record phase begins. OwnerId references on all migrated records are resolved at migration time using the finalised User lookup table.

Perfectview custom fields added to Relation, Activity, Case, and other objects are discovered during the discovery phase and mapped to equivalent Dynamics 365 custom fields. Field data types are mapped from Perfectview's type definitions to the closest Dynamics 365 field type (text to Text, date to Date, number to Number, checkbox to Two Options). Custom fields are deployed to the Dynamics 365 sandbox before migration begins and the mapping file is validated against the live schema.