Migrate from Cloze to Microsoft Dynamics 365 Sales

Cloze access verification and export method selection

We verify the customer's Cloze plan tier, user role (Manager or Administrator required for full exports), and current API beta access status. We send the API access request to [email protected] and simultaneously prepare the CSV export workflow from Settings > Import/Export as a fallback path. If the customer is on Business Platinum and uses Campaigns, we confirm campaign definitions for the written inventory deliverable. The scoping call produces a Cloze Access and Export Readiness Report.

Dynamics 365 environment preparation and schema design

We design the destination schema in the customer's Microsoft Dynamics 365 Sales environment. This includes provisioning custom fields on Contact, Account, and Opportunity to match Cloze custom fields; configuring Opportunity Sales Processes with stage values derived from the Cloze stage matrix; setting up Teams or Security Roles to match Cloze team structures; and designing the Lead-Contact-Account hierarchy. Schema is deployed to a Sandbox org first for validation against the exported data.

Data extraction, profiling, and cleansing

We extract People, Companies, Projects, Segments, Tags, and Timeline entries from Cloze via API or CSV export. Cloze's beta API uses a query parameter key rather than OAuth, which we handle with non-standard authentication. We profile the extracted data for duplicate records (People with matching email addresses, Companies with matching domain names), missing required fields (Contact without last name, Account without name), and stage value inconsistencies. We deliver a Data Quality Report before transformation begins.

Transformation, deduplication, and parent-record resolution

We transform Cloze records into Dynamics 365 format: People to Contact with AccountId resolved from Company domain matching; Companies to Account with domain as the dedupe key; Projects to Opportunity with stage mapped to the configured Sales Process. We run deduplication against the destination org before insert to avoid creating duplicate Contacts or Accounts. OwnerId references are resolved by email matching against the destination User table, with unmatched owners held in a reconciliation queue for the customer's admin to provision.

Production migration in dependency order with Bulk API

We run production migration in record-dependency order: Accounts (from Companies), Contacts (with AccountId resolved), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Tags (as multi-select or Topic), Activity history (Tasks, Events, EmailMessages via Bulk API 2.0 with batch chunking and exponential backoff), and Custom Fields (last to satisfy any lookup dependencies). Each phase emits a row-count reconciliation report before the next phase begins. We freeze Cloze writes during the final delta migration window.

Cutover, validation, and automation rebuild handoff

We enable Microsoft Dynamics 365 Sales as the system of record after the final delta sync. We deliver the Campaign and Workflow inventory document (as custom records with trigger and condition documentation) to the customer's admin team. We do not rebuild Cloze automations as Microsoft Dynamics 365 Sales Automation rules or Power Automate flows inside the migration scope. We support a five-day hypercare window where we resolve any record reconciliation issues. Post-migration admin rebuild of workflows, sequences, and forms is a separate engagement.