Migrate from Handyman to Microsoft Dynamics 365 Sales

Handyman customers map to Dynamics 365 Accounts. Customer name becomes Account Name, address fields map to Address composite fields, and primary contact links via Account's primary contact lookup. Multi-location customers create parent-child Account hierarchies in Dynamics 365, preserving the original Handyman location structure as separate child Accounts under a parent company Account.

Contact records on each Handyman customer map to Dynamics 365 Contacts. Email, phone, mobile, job title, and address fields translate directly. Contact links to Account via AccountId lookup. Multiple contacts per customer create separate Contact records all linked to the same Account.

Completed and in-progress Handyman jobs map to Dynamics 365 Opportunities. Job name becomes Opportunity Name, job total amount becomes Estimated Revenue, job date becomes Close Date, and job status maps to Opportunity Stage via value mapping. Open jobs become open Opportunities with target close dates from scheduled service dates.

Each Handyman job line item (labor, materials, equipment) becomes an Opportunity Product record linked to the parent Opportunity. Product Name maps to the Opportunity Product's product lookup, quantity and unit price map directly, and description carries over. Handyman service categories may require pre-creating Products in Dynamics 365 before migration.

Handyman technicians resolve to Dynamics 365 users by email match. Each user's records (Jobs, Customers) receive the matched SystemUser as OwnerId. Unmatched technicians are flagged before migration — the account either gets invited to Dynamics 365 first or their records are assigned to a fallback owner.

Handyman recurring service agreements have no native Dynamics 365 equivalent. We create a custom Agreement__c table with fields for agreement name, customer (Account lookup), start date, end date, frequency, and included services. The table links to Account and stores the original Handyman agreement ID for traceability.

Handyman asset records (customer equipment, serial numbers, service history) require a custom Asset__c table in Dynamics 365. Fields include Asset Name, serial number, make/model, customer (Account lookup), installation date, and last service date. Asset links to Account and inherits ownership from the customer Account.

Handyman job notes, photos, and attachments migrate as Dynamics 365 Annotations (Notes) on the related Opportunity. Original file names and creation timestamps are preserved in the annotation metadata. Inline images embedded in notes are extracted, downloaded, and rehosted in Dynamics 365's SharePoint-integrated document storage, with links preserved in the annotation text.

Handyman job statuses (Scheduled, In Progress, Completed, Cancelled) map to Dynamics 365 Opportunity Stages. We create a stage mapping table before migration: Scheduled maps to 'Qualification', In Progress maps to 'Value Proposition', Completed maps to 'Closed Won', Cancelled maps to 'Closed Lost'. Original Handyman status timestamps are preserved in custom datetime fields.

Handyman invoices cannot map directly to Dynamics 365 Sales — Sales has Orders and Invoices but they require integration with Business Central for full accounts receivable functionality. We migrate invoice records as custom Invoice__c records preserving invoice number, amount, date, and line items. For full AR capability, a Business Central integration is required post-migration.

Any Handyman custom fields on the customer record map to custom columns on the Account table in Dynamics 365. Field type translation applies: text fields become Text, date fields become Date, pick-list values become Option Sets. The schema is created in Dynamics 365 before migration runs.

Handyman custom fields attached to jobs map to custom columns on the Opportunity table. Same type translation logic as customer properties applies. Handyman stores some properties as JSON — these are flattened into separate text columns with original values preserved as a reference.