Migrate from HighQ to Microsoft Dynamics 365 Sales

HighQ Sites represent organizational work areas — they map to Dynamics 365 Accounts when the site corresponds to an external client or partner organization. When a Site represents an internal practice area rather than an external entity, we map it to a custom Site__c table in Dataverse so internal groupings are preserved without inflating the Account object.

For sites representing internal departments, practice groups, or matter-based structures rather than external accounts, we create a Site__c custom table in Dataverse. The table includes site name, description, status, created date, and owner fields. This avoids creating phantom Accounts for internal organizational units that have no CRM counterpart.

Each HighQ iSheet becomes its own custom Dataverse table. Column names and data types (text, number, date, picklist, user lookup) are translated to Dataverse column types. Relationships between iSheets are mapped as Dataverse lookup columns or many-to-many relationships. Sales Enterprise licensing is required when the total custom table count exceeds 15.

Individual rows in a HighQ iSheet migrate as rows in the corresponding Dataverse custom table. Primary key values are preserved as a Source_ID__c custom field for traceability and delta-run de-duplication. Dates, numbers, and pick-list values map directly where types match; text fields map directly regardless of length within Dataverse limits.

HighQ files attached to a Site or iSheet are re-uploaded as Note (Annotation) records in Dynamics 365. Each Note links to the parent record (Account, Contact, or custom table) via the objectid and objecttypecode fields. Files over 25 MB are split or linked to SharePoint/OneDrive via Dynamics' document management integration rather than stored as notes.

HighQ tasks map to Dynamics 365 Tasks with the same subject, description, due date, priority, and status. Original creation timestamps and owner IDs are preserved as custom fields (Original_Created__c, Source_Owner_ID__c) since Dynamics sets CreatedOn at migration time. Completed-on and completion notes carry over as the Task's actualend date and description respectively.

HighQ activity stream entries (posts, comments, document actions) are flattened into Note records on the parent Site or iSheet record. Each Note's body contains the post text, author name, and timestamp so the chronological record is preserved even though HighQ's threaded discussion model has no direct Dynamics 365 equivalent.

HighQ user accounts are resolved by email address against Dynamics 365 SystemUser records. Matched users become the OwnerId on migrated records. Unmatched users are flagged before migration so the team can either invite them to the Dynamics tenant or assign records to a fallback owner. HighQ role metadata (site-level permissions) does not migrate — Dynamics security roles are configured separately post-migration.

HighQ workflows and automation rules have no migration path to Dynamics 365. We export the workflow definition (rule conditions, triggers, and action sequence) as a JSON specification document that a Dynamics administrator or Power Automate builder can use as a rebuild reference. This is delivered alongside the data migration, not as part of it.

HighQ site-level permission assignments do not map to Dynamics 365 security roles or sharing rules. Dynamics security is role-based (Security Role assignment) and record-based (Sharing). We document the HighQ permission structure as a reference table so the Dynamics admin can configure equivalent access in the destination environment using the standard security model.

HighQ instance-level settings — notification preferences, branding, integration tokens, and API key configurations — have no counterpart in Dynamics 365 and must be re-established manually. We provide a configuration audit checklist mapping each HighQ setting to its Dynamics equivalent or flagging it as a manual setup item.

HighQ integrations with Thomson Reuters legal tools, DocuSign, or other third-party services do not transfer. Dynamics 365 supports Power Automate connectors and the Dataverse Web API for rebuilding integrations. We document each active HighQ integration endpoint so the team can identify Power Platform equivalents or custom connector builds post-migration.