Migrate from Sunbase Data to Microsoft Dynamics 365 Sales

Sunbase Contact records map to Dynamics 365 Contact. Standard fields (name, email, phone, address) transfer directly. Industry-specific contact properties (solar interest, financing status) require a pre-provisioned custom Contact field in Dynamics. We extract contact records from the CRM module, resolve any cross-references to Deals and Projects through the ID map, and insert into Dynamics with the parent Account resolved via the Company field match.

Sunbase Leads (from door-to-door forms, web capture, manual entry) map to Dynamics 365 Lead. Lead source, status, and assignment data transfer directly. Lead scores or rating values stored as custom fields migrate to a custom numeric field on Lead. Any Lead records tied to automation workflows are flagged separately since the automation logic does not migrate.

Sunbase Deals map to Dynamics 365 Opportunity. Deal value, pipeline stage, and associated contacts transfer. Pipeline stages in Sunbase map to a Dynamics Sales Process that we configure before migration. Closed-Lost and Closed-Won reason fields become custom Opportunity fields. If Sunbase Deal records link to multiple Contacts, we create a primary ContactOpportunityRelationship and attach secondary contacts via a related list migration script.

Sunbase Projects (installation or job-site operations) do not map directly to a standard Dynamics object. We evaluate during scoping whether to map Projects to a custom Project entity (using Dynamics custom objects) or to use Account records with project metadata in custom fields. We preserve project status, budget tracking, and linked Work Orders. The customer's choice depends on whether Projects represent billable entities (favoring custom entity) or customer locations (favoring Account).

Work Orders include permit info, task details, attachments, and system specifications. We map Work Orders to Dynamics 365 Case if the destination org includes Service Cloud or to a custom Work_Order__c entity. Permit tracking fields and system specifications migrate as custom fields on the destination entity. Linked employee assignments resolve via the User mapping created during owner reconciliation.

Sunbase Invoices migrate to Dynamics 365 Invoice. Line items, payment status, and linkage to the originating Project or Client transfer directly. Historical paid invoices migrate as closed invoices with the Paid status. If the customer uses Business Central for financial management, we map Invoice records to Invoice entities in Business Central rather than Dynamics Sales Invoice and note this in the scope document.

Sunbase Employee records (HR data, crew assignments) map to Dynamics 365 User records for employees who access the CRM and to Contact records for field staff without CRM access. Crew assignments and role metadata migrate as custom fields on User. GPS location history is extracted as a separate dataset and mapped to a custom entity or SharePoint document library depending on whether the customer wants it queryable within Dynamics.

Sunbase Appointments (customer-linked scheduling synced with Google Calendar) map to Dynamics 365 Appointment records. Appointment dates, times, assigned contacts, and status transfer directly. Calendar linkage (Google Calendar) is not transferable; appointments land in Dynamics without the external calendar sync, which the customer reconfigures through the Dynamics Outlook add-in post-migration.

Sunbase Documents (contracts, financing applications, permits) are extracted as binary files with their parent record associations preserved in a manifest. We map documents to SharePoint via Dynamics 365 Document Locations (SharePoint integration enabled) or to Notes with file attachments depending on the customer's SharePoint configuration. Upload dates and association metadata (Contact, Deal, Project link) migrate as metadata on the document record.