Migrate from Glaze CRM to Microsoft Dynamics 365 Sales

Discovery and data extract coordination

We audit the source Glaze CRM instance through a customer-provided schema audit and sample record export. Because Glaze CRM has no public API, we guide the customer in requesting a full CSV or database dump from Softuvo Solutions. We document the existing field inventory, pipeline stages, custom field types (inferred from sample data), and record volumes across Contacts, Companies, Deals, Leads, and Tasks. We also confirm the Microsoft Dynamics 365 Sales edition (Professional at $65/user/mo or Enterprise at $105/user/mo) appropriate for the customer's scope.

Schema design and field mapping

We design the Microsoft Dynamics 365 Sales destination schema using the customer's schema audit. This includes creating custom fields (with type-mapped Dynamics 365 field types), configuring Sales Processes with stage values matched to the Glaze CRM pipeline, creating Record Types for multi-pipeline scenarios, and setting up page layouts per Record Type. Schema is deployed into a Dynamics 365 Sandbox first for validation. We build the field mapping spreadsheet that pairs each Glaze CRM field against its Dynamics 365 equivalent, flagging any multi-select conversions, date format normalizations, and custom field creations required.

Owner reconciliation and User provisioning

We extract every distinct Glaze CRM User referenced on Contacts, Companies, Deals, Leads, and Tasks and match by email against the Dynamics 365 destination org's User table. Owners without a matching User are placed in a reconciliation queue. The customer's Dynamics 365 admin provisions any missing Users before record migration begins. Owner resolution is a prerequisite for all subsequent import phases because OwnerId is a required reference on most standard objects.

Sandbox migration and reconciliation

We run a full migration into a Dynamics 365 Sandbox using production-like data volume. The customer's admin or RevOps lead spot-checks 25-50 records against the Glaze CRM source, verifies that pipeline stages align, confirms custom field data populated correctly, and signs off the schema and mapping before production migration begins. Any mapping corrections, type inference errors, or missing required fields are addressed here.

Production migration in dependency order

We run production migration in record-dependency order: Users (validated), Accounts (from Glaze CRM Companies), Contacts (with AccountId resolved via company reference), Leads (with OwnerId resolved), Opportunities (with AccountId, ContactId, OwnerId, and Sales Process resolved), Tasks (with Regarding resolved against parent records). Each phase emits a row-count reconciliation report before the next phase begins. We use the Dynamics 365 Dataverse API with batch chunking and rate-limit handling to manage API throughput during high-volume phases.

Cutover, validation, and automation rebuild handoff

We freeze Glaze CRM writes during cutover and run a final delta migration of any records modified during the migration window. We deliver a written inventory of Glaze CRM automation rules, workflow configurations, and any pipeline logic requiring rebuild in Microsoft Dynamics 365 Sales or Power Automate. We do not rebuild these as code inside the migration scope. We support a brief hypercare window where we resolve any reconciliation issues raised by the customer's team post-cutover.