Migrate from Ziggu to Microsoft Dynamics 365 Sales

Ziggu Clients map 1:1 to Dynamics 365 Contacts. The Contact's parent AccountId is set to the migrated Account (from the Ziggu Project). Clients without a project association receive a default 'Unassigned' Account record. Email addresses are required for Dynamics 365 Activity correlation.

Ziggu Projects map to Dynamics 365 Accounts. The Account Name is the project name, and the Address fields are populated from Ziggu's project location data. Projects without a company entity in Ziggu are migrated as standalone Accounts. All account fields, including phone and website, are set where available. Primary contact assignments are determined from the Ziggu project's client list.

Ziggu Units have no native Dynamics 365 equivalent. We create a custom Property_Unit__c Dataverse table linked to the Account (Project) via a lookup field. Fields include Unit_Name, Floor_Area, Price, Status, and Bedrooms_Bathrooms__c. The table also stores the project reference so each unit can be associated with its parent account. Additional custom fields can be added later through Power Apps maker portal.

Ziggu Reservations map to Dynamics 365 Opportunities with RecordTypeId='Reservation'. The Opportunity Amount is set from the Unit price. StageName maps to Ziggu's reservation status (Inquiry, Reserved, Contract Signed). Custom fields on the Opportunity capture unit reference and reservation date. The Opportunity also inherits the Project_Account__c lookup for continuous reporting across the development pipeline.

Ziggu Contracts that represent legal agreements map to Dynamics 365 Quotes (if still negotiating) or Orders (if executed). The Quote/Order line items reference the Property_Unit__c record. Contract terms and clauses are stored in a custom text field since Dynamics 365 has no native clause library.

Ziggu Conversation threads have no native Dynamics 365 equivalent. A custom Client_Conversation__c table is created linked to Contact and Account. Each conversation becomes a record with Subject, Body, Timestamp, and Direction (Inbound/Outbound). Original message threading is preserved in the Body field as a formatted text block.

Ziggu documents migrate to SharePoint document libraries associated with the Account (Project) and Property_Unit__c records. We re-upload files to SharePoint and create a Note record in Dynamics 365 referencing the SharePoint URL so users see document links within the CRM forms.

Ziggu Tasks map to Dynamics 365 Tasks. Subject, Description, Due Date, Priority, and Status migrate directly. Owner resolution uses email match against Dynamics 365 users. Completed Tasks retain their completion timestamps as custom datetime fields since Dynamics 365 CreatedDate is set at migration time.

Ziggu Approvals (client decisions, milestone sign-offs) have no Dynamics 365 native equivalent. A custom Approval_Request__c table is created linked to Account, Contact, and Property_Unit__c. Fields include Approval_Type, Decision, Decision_Date, and Comments. Pending approvals are flagged for manual follow-up post-migration. This structure preserves audit history and allows Power Automate workflows to trigger notifications or escalations based on approval status.

Ziggu Survey responses have no native Dynamics 365 equivalent. A custom Survey_Response__c table captures survey name, respondent Contact, submission date, NPS score, and individual question responses as custom text fields. Survey logic must be rebuilt in Dynamics 365 Customer Voice (additional license) post-migration.

Ziggu Financials (payment schedules, invoices, balances) migrate as a custom Payment__c table linked to Account and Property_Unit__c. Fields include Payment_Amount, Due_Date, Paid_Date, Status, and Payment_Type. Dynamics 365 Finance integration requires a separate implementation of Dynamics 365 Business Central if full accounting is needed.