Migrate from GBuilder to Microsoft Dynamics 365 Sales

GBuilder Contact maps one‑to‑one to D365 Contact, with the primary company association transferred to the Parent Account lookup. Contacts linked to multiple companies are represented through the D365 AccountContactRelationship entity or a custom junction table, ensuring each affiliation is retained. Original create timestamps and owner assignments are preserved in custom datetime and owner fields for reporting continuity.

GBuilder Company maps to D365 Account. The primary contact flag on GBuilder translates to the Primary Contact lookup on the D365 Account record. Parent-company hierarchies in GBuilder map to the Parent Account lookup in D365; circular references are flagged and resolved before commit.

GBuilder Deal maps directly to D365 Opportunity, copying the deal name into Opportunity.Name, the amount into EstimatedRevenue, and the close date into EstimatedCloseDate. The deal owner resolves to D365 OwnerId via email lookup, and any unmatched owner is flagged for admin action. Deal stage labels are translated to D365 StatusCode Option Set values, and a Business Process Flow is attached to enforce the pipeline progression.

GBuilder pipeline stages become D365 Opportunity Status and StatusCode Option Set values. A D365 Business Process Flow is created per GBuilder pipeline so each pipeline has its own stage progression UI. FlitStack generates the BPF as part of the migration plan.

GBuilder Project is a construction or project-specific object with no direct D365 equivalent. FlitStack creates a custom Dataverse table (new_Project__c) and maps project fields individually. If the D365 instance has Project Operations licensed, Project Service Administration entities are used instead.

GBuilder tasks and activity records map to D365 Task entities. The subject, description, due date, and regardingObjectId (pointing to the parent Contact, Account, or Opportunity) are preserved. Activity type discrimination (call vs. email) uses the Category or Type field on the D365 Task.

GBuilder notes migrate as D365 Annotation records attached to the parent Contact, Account, or Opportunity. The note text (document body), subject line, and created‑on timestamp are preserved exactly. Notes that exceed D365's inline size limit are stored as file annotations in SharePoint, with the Annotation record pointing to the SharePoint URL so users can open the content directly from the D365 form.

GBuilder file attachments are downloaded from the source API and uploaded to D365 SharePoint document locations that are tied to the parent record's logical folder (Contact, Account, or Opportunity). Files under the 10 MB limit are stored as D365 Email attachments on the regardingObjectId record for quick access. Original filenames, upload timestamps, and owner information are retained in the SharePoint metadata so the audit trail remains intact.

Every GBuilder custom property maps to a typed custom field in D365. The migration plan includes a field creation manifest (schema name, data type, Option Set binding where applicable) that the D365 admin pre-creates. Custom fields follow the new_ schema prefix convention.

GBuilder owner records resolve to D365 SystemUser rows by matching the owner email address to the Dataverse systemuser table. FlitStack generates a pre‑flight owner resolution report that lists matched users (green), unmatched owners (red), and a recommended fallback owner for each red entry. The admin must create D365 user accounts or designate a fallback before migration proceeds; no record commits with an unresolved owner.

If GBuilder stores leads separately from contacts, they map to D365 Lead. The lead status pick-list in GBuilder maps to D365's LeadStatus Option Set value-by-value. Upon lead qualification, D365 entity mappings carry custom fields from Lead to Contact using the OOB field mapping UI.

GBuilder quotes and proposals map to D365 Quote records that are linked to the parent Opportunity. Each quote line item becomes a QuotedProduct record, preserving product name, quantity, unit price, discount percentage, and tax amount. Pricing adjustments and global discounts on the quote are transferred field‑by‑field, and the Quote's status follows the D365 Sales process so the quote lifecycle is visible in the opportunity pipeline.