Migrate from Agencyzoom to Microsoft Dynamics 365 Sales

AgencyZoom leads map directly to Dynamics 365 Lead. Source create date, owner, and lifecycle stage preserve as custom fields. Lead status pick-list values map value-by-value to Dynamics StatusCode. Phone and email fields carry over without transformation. Original AgencyZoom lead ID is stored as a reference field for reconciliation.

AgencyZoom contacts map 1:1 to Dynamics 365 Contact. Each contact requires an AccountId — if no primary company exists in AgencyZoom, we create a placeholder 'Unassigned Account' record in Dynamics and link contacts to it. Original AgencyZoom create date stored as Original_Create_Date__c custom field.

AgencyZoom companies map to Dynamics 365 Account. Parent-child hierarchies translate via Account.ParentId. When a contact links to multiple companies, the primary company becomes the AccountId and secondary links become Account Contact Relationship records in Dynamics for each additional association.

AgencyZoom Policy has no direct Dynamics 365 Sales equivalent. We map policy records as custom fields on the Account (for policy-holder data) and Opportunity (for policy-quote data). Fields include Policy_Number__c, Carrier__c, Policy_Type__c, Premium__c, Effective_Date__c, Expiration_Date__c, and Policy_Status__c. A separate Policy custom table is available at Enterprise tier.

AgencyZoom Sales Pipeline maps to Dynamics 365 Opportunity with a corresponding Sales Process. Each pipeline stage in AgencyZoom produces a StageName entry in the Sales Process. Probability and forecast category re-applied based on Dynamics defaults unless you provide stage-mapping rules.

AgencyZoom Service Pipeline tracks service tickets and renewal work. We map open tickets to a custom Service_Ticket__c table or as custom fields on the Account. Stage names (New, In Progress, Resolved) map to Opportunity StageName or a custom pick-list on the Account — your admin chooses based on how your team uses service records.

AgencyZoom Onboarding Pipeline manages client onboarding steps. We map the pipeline to an Opportunity with stage-based Tasks. Each stage transition in AgencyZoom becomes a Task record with the original stage name as the subject and the completion date preserved. Tasks link to the Opportunity's Account.

AgencyZoom tasks — both manual and those generated by lifecycle automation — map to Dynamics 365 Task. Original timestamps, due dates, owners, and completion status carry over. Automated-task lineage (which automation created it) is preserved as a custom note field for your admin's reference during Power Automate rebuild.

AgencyZoom notes migrate to Dynamics 365 Note (modern notes, not legacy). Rich-text formatting is preserved through the transfer. Notes attach to the parent record (Lead, Contact, Account, or Opportunity) using ObjectId and ObjectTypeCode references matching the Dynamics schema.

AgencyZoom file attachments re-upload to Dynamics 365 SharePoint document locations linked to the target Account or Opportunity. Files under 25 MB attach directly; larger files chunk and re-upload with the original filename preserved. Inline images in notes download and rehost as SharePoint assets.

AgencyZoom custom fields (carrier IDs, coverage amounts, commission rates, etc.) migrate as Dynamics 365 custom fields on the appropriate table. Field type maps by data type: text to Text, numbers to Number or Decimal, dates to DateTime, pick-lists to Picklist. All custom fields are prefixed az_ for traceability during validation.

AgencyZoom carrier associations (links to insurance carriers) have no native Dynamics 365 equivalent. We store carrier name as Carrier__c text field on Account and carrier ID as Carrier_ID__c. At Dynamics 365 Sales Enterprise tier, a custom Carrier table with a lookup relationship to Account can be created during the migration.