Migrate from Upvise to Microsoft Dynamics 365 Sales

Upvise Contact maps 1:1 to Dynamics 365 Contact with direct field correspondence for standard attributes. All name variants (first, last, full name), email address, phone numbers, job title, and address components carry over directly without transformation. The primary company link in Upvise — stored as a text reference — becomes the AccountId lookup in Dynamics 365, linking to the corresponding Account record after accounts are loaded. Owner assignment resolves via email match to SystemUser records.

Upvise Company maps directly to Dynamics 365 Account, serving as the organizational parent entity for both contacts and opportunities. Company domain and industry fields map to Account.WebsiteURL and Account.IndustryCode respectively, with value-by-value translation where Upvise pick-list values differ from Dynamics 365 optionsets. The industry translation table accounts for Upvise's smaller industry vocabulary by mapping to the nearest matching Dynamics optionset entry, ensuring consistent reporting across the migrated dataset.

Upvise Job functions as the deal and proposal record, mapping to Dynamics 365 Opportunity through a set of named transformations. Job.name maps to Opportunity.Name, Job.amount becomes Opportunity.EstimatedValue, Job.status translates to Opportunity.StateCode and StatusCode combinations, and Job.customer maps to Opportunity.CustomerId as an Account lookup. Close dates transfer directly as Opportunity.CloseDate. Any custom pipeline-stage field on the Upvise Job maps to Opportunity StageCode with probability and forecast category values re-applied from the Dynamics 365 side.

Each line item attached to an Upvise Job — whether representing products quoted or services rendered — maps to a distinct Opportunity Product record linked to the parent migrated Opportunity. Unit price and quantity fields transfer directly to their corresponding Opportunity Product attributes. If Upvise stores bundled or package pricing as a single line item, the migration flattens these into individual Opportunity Product rows so each product appears separately on the Opportunity in Dynamics 365.

Upvise Notes map directly to Dynamics 365 Annotations within the Note/Annotation entity, preserving the original created-on timestamp, full note text content, and owner assignment from the source record. If Upvise notes contain file attachments, those files re-upload as NoteAttachment records linked to the corresponding Annotation, maintaining the attachment-to-note relationship from the original Upvise structure. The original author information is retained in the Annotation.OwnerId field.

Upvise Form responses have no direct Dynamics 365 equivalent. We create a custom Dataverse table named FormSubmission with columns derived from each Form field definition, using the new_ prefix convention for custom attributes. Form metadata including the form name, submission date, and submitting contact reference map to custom columns on the new table. The FormSubmission table links to Contact via a new_contactid lookup so submissions can be associated with the respondent's CRM record.

Upvise custom fields defined on the Contact module become custom columns on the Dynamics 365 Contact table using the new_ column prefix. On Sales Enterprise these custom columns are created without restriction against the Dataverse Contact table. On Sales Professional the migration first checks the destination org's total custom-table count against the 15-table limit to ensure the migration will not exceed licensing constraints before proceeding.

Upvise custom fields on the Company module map to custom columns on the Dynamics 365 Account table using the new_ naming convention. Before creating these columns, we validate that the destination organization's custom table count permits direct column addition without exceeding the Sales Professional 15-table cap. If the destination is on Sales Professional and the cap is at risk, we flag the overflow in the pre-migration plan for resolution before the migration run executes.

Upvise Job custom fields map to custom columns on the Dynamics 365 Opportunity table. Dynamics 365 permits unlimited custom columns on standard entities like Opportunity regardless of whether the environment runs Sales Professional or Sales Enterprise — this applies to columns on standard entities only, not custom tables. Therefore this particular custom field mapping is always viable without pre-migration capacity planning or table-cap concerns.

Upvise users assigned as job owners or contact owners resolve by email match against Dynamics 365 SystemUser records. The migration extracts all Upvise owner email addresses, queries the Dynamics 365 environment for matching SystemUser records, and maps matched users directly. Unmatched owners are flagged with record counts in the pre-migration User Resolution Report — you either provision a Dynamics 365 license and account for each unmatched user or reassign their records to a fallback owner before the run commits.

Upvise file attachments on contacts, companies, or jobs re-upload to Dynamics 365 through a conditional routing mechanism. If the Dynamics 365 environment has SharePoint integration enabled and server-based SharePoint authentication configured, files route to SharePoint document libraries with a folder hierarchy mirroring the Upvise record structure. If SharePoint integration is not configured at migration time, files attach directly to the Note record instead — fully functional but stored within Dynamics rather than in SharePoint document management.

Upvise Projects have no standard equivalent in Dynamics 365 Sales, so we create a custom Dataverse Project table with columns representing project name, status, start and end dates, and linked Contact and Account lookups. The Project table also includes a custom lookup field pointing to the related Opportunity so project records maintain context with the deals they support. This custom table operates like any standard Dataverse table and can be extended with additional columns or included in Power Apps and Power BI reports.

Dynamics 365 Business Process Flows encode stage gates and process steps for Opportunities, guiding sales reps through defined pipeline stages with required fields and visual progression. No equivalent Upvise feature exists to migrate since Upvise does not expose workflow or process automation data through its API. We provide a BPF design template populated with stage names derived from your Upvise job-status values, allowing your Dynamics 365 administrator to configure stage progression, probability mapping, and required field gates in the BPF designer after the data lands.