Migrate from mQuest to Microsoft Dynamics 365 Sales

mQuest contacts migrate as Dataverse Contact records. Dynamics 365 Sales requires an AccountId on most contact records — if the mQuest contact has no associated company, FlitStack attaches it to a default 'Unassigned Account' record in Dynamics 365 Sales to satisfy the lookup requirement.

If mQuest stores both qualified and unqualified contacts in one object, FlitStack splits on a status or lifecycle field: records marked as customers in mQuest become Dynamics 365 Sales Contacts; all others route to Lead for follow-up qualification. This routing rule is configurable before migration runs.

mQuest company records map to Dynamics 365 Sales Account entities. Parent‑child hierarchies in mQuest translate to the ParentAccountId lookup on the Account record, preserving the original corporate structure. When a contact in mQuest references multiple companies, FlitStack collapses the association to a primary AccountId and creates additional Account‑Contact relationships, while storing the original company references in a custom field for audit purposes.

mQuest deal records map to Dynamics 365 Sales Opportunity entities in Dataverse. FlitStack translates deal fields such as amount, close date, and stage to the corresponding Opportunity attributes (estimatedvalue, estimatedclosedate, stageid). Because the Opportunity record requires an AccountId or ContactId lookup, FlitStack resolves the parent reference before inserting each deal, populating the Regarding field. The original mQuest deal identifier is stored in a custom column for traceability.

mQuest pipelines map to Dynamics 365 Sales Business Process Flows. Each mQuest pipeline becomes a separate Business Process Flow instance, and the pipeline stages become stage names within that process. Stage transitions and timestamps are preserved as process stage history in Dataverse.

Stage names from mQuest are mapped value-by-value to Dynamics 365 Sales Opportunity StageName picklist values. Each mQuest stage is assigned a matching Dynamics 365 Sales stage; if no exact match exists, FlitStack selects the closest equivalent and flags it for admin review before migration.

mQuest custom objects map one‑to‑one to custom Dataverse tables in Dynamics 365 Sales. Before loading data, FlitStack generates a schema creation script that defines each table, its columns (using the new_ prefix), data types, and indexes. Relationships between custom objects are expressed as Dataverse lookup or many‑to‑many relationships, and picklist values are populated in the environment. This ensures the object structure mirrors the mQuest model while conforming to Dataverse conventions.

mQuest engagement records are decomposed into the corresponding Dataverse activity entities. Phone calls become PhoneCall, emails become Email, meetings become Appointment, and notes become Note. Each activity retains its original timestamp, owner (resolved by email match), and RegardingId pointing to the parent Account or Contact.

mQuest file attachments are re‑uploaded to Dynamics 365 Sales as Note attachments (Annotation entity) or to SharePoint when the target environment has SharePoint integration enabled. FlitStack preserves the original file name and links each attachment to its parent record (Contact, Account, or Opportunity) via the RegardingId lookup. Files larger than the 32 MB Dataverse limit are stored in SharePoint and linked in the annotation.

mQuest owner IDs are resolved against Dynamics 365 Sales users by email address. Unmatched owners are flagged before migration — teams either provision the user in Dynamics 365 Sales first or assign records to a fallback owner. No record lands without a valid OwnerId.

mQuest product or line‑item records map to the Dynamics 365 Sales Product catalog and to Opportunity Product junction records on opportunities. FlitStack translates product name, description, and SKU into the Product entity, and links each product to the price list via UoMSchedule and PriceListItem entities, preserving unit, quantity, and pricing details. If mQuest stores bundles, each bundle component is exploded into Opportunity Product lines with a parent‑child relationship in Dataverse.

mQuest task records migrate as Dataverse Task entities. FlitStack maps the task subject, description, due date, and owner to the corresponding Task attributes, and sets the regardingId to the parent Contact or Account record to keep the task visible on the record timeline. Status and priority values are translated to Dynamics 365 Sales picklist values, and sub‑tasks are converted into separate Task records linked by a parent‑task lookup.