Migrate from EverPro to Microsoft Dynamics 365 Sales

EverPro contacts map directly to Dynamics 365 Contacts. The primary company association becomes AccountId lookup — if the contact's company exists in EverPro as a separate record, we resolve the Account GUID first. Contacts without a company link attach to a default 'Unassigned Account' record.

EverPro company records map to Dynamics 365 Accounts. Company address, industry classification, employee count, and annual revenue fields translate directly to the corresponding Account columns. Parent-child company hierarchies in EverPro use the ParentAccountId field in Dynamics 365 to replicate the same hierarchical relationship structure. We validate that all required Account columns exist before mapping begins.

EverPro jobs have no direct Dynamics 365 CRM equivalent — they represent service work orders with status, technician assignment, and line items. We create a Dataverse custom table (FieldServiceJob) and map job ID, status, created date, and technician owner. The job's associated contact and company become lookups to Contact and Account.

Individual service line items on a job (parts used, labor hours, service type) become rows in a ServiceHistory custom table linked to FieldServiceJob. Service type codes from EverPro map to a Choice column in Dynamics 365. Original service date and completion notes preserve as datetime and text columns.

EverPro's Customer Loyalty module tracks points balance, tier status (Bronze, Silver, Gold, Platinum), and redemption history per customer. We create a LoyaltyMetric Dataverse table linked to the Contact record, storing current points balance, program tier name, and last activity date as custom columns. Tier-update rules require Power Automate flows post-migration.

EverPro BI dashboards expose funnel metrics, revenue-per-technician, and service KPIs. These export as raw metric snapshots stored in a BIMetric custom table with columns for metric name, value, period, and source record link. Dynamics 365's built-in reporting and Power BI consume this data after migration.

EverPro technicians and contact owners are users in the system. We resolve each EverPro user by email match against Dynamics 365 Users. Unmatched users are flagged before migration — the team either provisions a Dynamics 365 license or assigns records to a fallback owner.

EverPro job attachments (photos, signatures, invoices, work orders) export as binary files and re-upload to SharePoint via Dynamics 365's native SharePoint integration. File references become Note records with an absolute URL pointing to the SharePoint document location. The original filename and MIME type are preserved in the Note record for reference.

EverPro invoices can split into two paths: if the invoice relates to a closed Opportunity, line items become Opportunity Product records in Dynamics 365. If invoices represent service billing without a sales opportunity context, we create a custom Invoice Dataverse table linked to the Account.

EverPro allows custom properties on BI dashboard configurations that extend beyond standard metric definitions. We export these as named-value pairs stored in the BIMetric custom table's extended columns. Each unique custom property name from EverPro requires a corresponding column definition in the Dynamics 365 schema before migration, so all custom BI properties must be inventoried during the schema audit phase.