Migrate from Jobber to Microsoft Dynamics 365 Sales

Jobber clients map directly to Dynamics 365 Contacts. The client's primary email, phone, and name become Contact fields. If the Jobber client is a business entity without a named contact, we create a Contact record using the client name and mark the record type accordingly.

Jobber clients that represent business entities merge into Dynamics Account records — the business name becomes Account.Name, the primary address becomes the Account address, and the client Contact becomes a related Contact with primary account linkage. This ensures the business entity is available for Opportunities and reporting hierarchies in Dynamics.

Jobber properties are service locations associated with a client. Each property becomes a secondary Account record linked to the primary client Account via the Parent Account field, preserving the property-specific address and property-type custom fields from Jobber. This maintains location-specific service history accessible through the account hierarchy in Dynamics reporting.

Jobber jobs translate to Dynamics Tasks or custom Service Activity records. The job's scheduled date becomes the Task scheduled end, assigned team member resolves to a Dynamics user by email match, and job status maps to Task statecode with value translation for each Jobber status.

For jobs that represent billable service contracts or project work, we create Opportunities with a custom field linking back to the original Jobber job ID. This lets teams track service revenue through the Dynamics pipeline model without losing the field-service context.

Jobber quotes map to Dynamics Quotes. Quote line items become Quote Details with product, quantity, and unit price. The Jobber quote expiry date maps to the Dynamics Quote expires-on field. Status translation maps accepted, declined, and expired quotes to the corresponding Dynamics statuscode values.

Jobber invoices with payment status of paid map to Dynamics SalesOrders with statuscode set to invoiced. Unpaid Jobber invoices become Dynamics SalesOrders in submitted or active status. The Jobber payment date and payment method are preserved as custom fields on the SalesOrder record.

Jobber team members resolve to Dynamics 365 SystemUser records by email address. Unmatched team members are flagged before migration — either invited to Dynamics first or assigned to a fallback user. Active/inactive status in Jobber maps to the enabled/disabled state in Dynamics.

Jobber custom fields on clients become Dataverse custom columns on the Contact entity. Field type is preserved: text fields become nvarchar, number fields become integer or decimal, date fields become datetime. We create the custom columns in your Dynamics solution before data loads.

Jobber property custom fields map to custom columns on the Account entity in Dataverse. Property-type classifications, inspection data, equipment lists, or warranty information stored as Jobber property fields become nvarchar or the appropriate Dataverse data type on the Account record, preserving all property-specific context in the target system.

Job-level custom fields such as work type codes, authorization numbers, site access instructions, or equipment serviced migrate as custom columns on the Task entity. We map and validate them before migration so the full job context and operational details follow the service record into Dynamics.

Jobber file attachments on clients, properties, and jobs become Note (Annotation) records in Dynamics tied to the corresponding Contact, Account, or Task. File size limits per Dynamics apply. We re-upload files to the Dynamics instance storage and verify attachment relationships post-migration.

Jobber automations for quote reminders, client notifications, and job status alerts do not have a Dynamics equivalent that carries over automatically. We export the automation definitions as a reference document for rebuilding in Power Automate, which handles similar triggers and actions natively.