Migrate from Visionary to Microsoft Dynamics 365 Sales

Direct map to Dynamics 365 Contact table within Dataverse. The AccountId lookup on Contact requires a Visionary Company record to exist first so the lookup resolves correctly. Contacts without a primary company attach to a default placeholder account. We also verify that the email address on each Contact is unique within the target environment to avoid duplicate detection issues in Dynamics 365.

Direct map to Dynamics 365 Account table. Parent-child company hierarchies in Visionary map to Account.ParentAccountId. Multi-company associations on Visionary contacts collapse to one primary AccountId plus Account Contact Relationships. During migration we also enforce naming conventions for Account names and truncate any that exceed the 120-character limit enforced in Dynamics 365. Additionally, we flag any accounts with missing address data so that administrators can fill in required fields post-migration.

Direct map to Dynamics 365 Opportunity table. The pipeline and stage from Visionary map to the Sales Process and StageName on Opportunity. Each Visionary pipeline becomes a separate Business Process Flow in Dynamics 365 Sales. We also preserve the original probability percentages from Visionary stage definitions as custom forecast values unless the Enterprise forecasting module is active.

Visionary pipeline definitions translate to Dynamics 365 Sales Processes. Each pipeline requires a corresponding Business Process Flow in Dynamics 365 Sales Enterprise. Professional tier users need simplified stage mapping without process flows. During the translation, we capture any custom stage order and rename stages to match your existing terminology, ensuring the process flow reflects your sales cycle precisely.

Visionary stage names map value-by-value to Dynamics 365 Opportunity StageName pick-list values. Probability percentages attached to Visionary stages re-apply as manual forecast values in Dynamics 365 if the Enterprise forecasting module is not enabled. We also log any unmapped stage names and provide a mapping worksheet for your administrator to complete before final data load.

Visionary call records map to Dynamics 365 PhoneCall activity with Direction, Subject, and Description preserved. OwnerId resolves by email match to Dataverse SystemUser. Regarding lookup connects to the parent Contact or Opportunity. During the load we also verify that the phone number format complies with Dynamics 365 validation rules and flag any records with missing required fields for manual correction.

Visionary email activities map to Dynamics 365 Email activity with Subject, Description, and direction preserved. Attachments on Visionary emails re-upload to Dynamics 365 SharePoint or Notes attachments based on admin configuration. We also check attachment file sizes during the upload phase; any file exceeding the 25MB limit is automatically routed to SharePoint document libraries with the appropriate Document Location linkage.

Visionary meeting records map to Dynamics 365 Appointment with original Start Time, End Time, Location, and Required Attendees preserved. OwnerId resolves by email to SystemUser. During migration we also validate that the meeting duration does not exceed Dynamics 365's maximum appointment length and that any missing attendee email addresses are flagged for correction before final import.

Visionary notes migrate to Dynamics 365 Annotation entity with IsDocument=false. Rich-text formatting in Visionary notes converts to plain text with HTML preservation where supported. Parent object lookup routes to the original record. We also preserve the original note creation timestamps as custom fields to maintain full historical context in the target system.

Visionary custom properties without a Dynamics 365 native equivalent create custom columns on the appropriate Dataverse table. Field type mapping applies: Visionary string to Text, number to Whole Number or Decimal, date to DateTime, pick-list to Choice. We also record the original Visionary field display names in a custom metadata table to assist with future reporting and user training.

Visionary owner records resolve to Dynamics 365 SystemUser by email match. Unmatched owners flag before migration so the team can invite them to Dynamics 365 or assign a fallback user. Disabled owners map to a placeholder owner record. We also verify that the resolved SystemUser records have the appropriate security roles assigned for data access after migration.

Visionary file attachments migrate to Dynamics 365 Note or SharePoint Document Location depending on the destination configuration. File size limits of 25MB per file apply from Dynamics 365; larger files require chunked upload or SharePoint storage configuration. We also perform a pre-upload validation to ensure each file's MIME type is supported by SharePoint and log any files that exceed the library's storage quota.