Migrate from Workbooks to Microsoft Dynamics 365 Sales

Workbooks Organisation maps to Microsoft Dynamics 365 Sales Account with a direct field-level correspondence on standard fields including Name, Website, Industry, Classification, and Address fields. Custom fields defined on the Organisation record type map to custom Account fields in Microsoft Dynamics 365 Sales . The Organisation record is created first in the migration sequence so that the AccountId lookup on People is satisfied when Contact records are inserted. iFrame custom fields export as URL strings and are stored as text fields in Microsoft Dynamics 365 Sales ; the embedded content does not transfer.

Workbooks People map to Microsoft Dynamics 365 Sales Contact. The Organisation lookup on People becomes the AccountId lookup on Contact, preserving the parent-company relationship at migration time. First Name, Last Name, Email, Phone, Job Title, and any custom Person-level fields transfer directly. We resolve the AccountId reference before inserting Contact records to avoid orphaned contacts without a parent Account.

Workbooks Opportunities map to Microsoft Dynamics 365 Sales Opportunity with stage, probability, estimated close date, and owner preserved. The dealstage property maps to StageName and the Workbooks pipeline assignment maps to a Microsoft Dynamics 365 Sales Record Type or Sales Process that we configure before migration. Closed-Lost and Closed-Won reasons from Workbooks become custom loss reason and win reason fields on Opportunity. Workbooks does not enforce a hard pipeline limit, but Microsoft Dynamics 365 Sales Professional supports unlimited Record Types and Sales Processes; multiple Workbooks pipelines map to separate Record Types on Opportunity.

Quotations are available on Workbooks CRM Business tier and above only. If the source subscription is on CRM or CRM Pro, quotation objects do not exist in the export and this mapping is skipped. When available, the quotation header and line items migrate to Microsoft Dynamics 365 Sales Quote records (available on Sales Professional tier) or as Opportunity records with line items, depending on the customer's workflow preference. PDF attachments stored against quotations are downloaded and reattached as Notes or ContentDocument records to the destination record.

Invoices are available on Workbooks Business tier and above. Microsoft Dynamics 365 Sales Professional and Enterprise do not include a native accounts receivable invoice object. We check whether the customer has Dynamics 365 Business Central available. If yes, Workbooks invoice data routes to Business Central Invoices. If no, we create a custom Invoice and Invoice Line object in Microsoft Dynamics 365 Sales with invoice header data, line items, and payment status migrated, and attach Workbooks invoice PDFs as Notes to the custom record. Order-to-invoice linkage is preserved as a reference note.

Workbooks Activities (calls, emails, meetings, and tasks) map to Microsoft Dynamics 365 Sales Task and Event objects. Calls map to Task with TaskSubtype set to Call; emails map to Task and EmailMessage records; meetings map to Event; standalone tasks map to Task. Activity timestamp, duration, subject, and description transfer. The parent-record lookup (WhoId and WhatId) resolves against migrated Contact and Opportunity records using the lookup tables built during the earlier phases. Workbooks uses separate objects for each activity type; Microsoft Dynamics 365 Sales consolidates into Task and Event, so type differentiation happens via TaskSubtype and record type rather than separate object tables.

Workbooks Lead records map directly to Microsoft Dynamics 365 Sales Lead. Lead Status, Lead Source, Rating, and Owner assignment transfer as standard Lead fields. Workbooks does not use a lifecycle stage concept for leads, so no split rule is required as it is in HubSpot-to-Salesforce migrations. Any scoring data from Workbooks custom fields maps to a custom Lead field for use in Dynamics lead scoring.

Workbooks Cases map to Microsoft Dynamics 365 Sales Case with case status, priority, assigned user, related Organisation, and description preserved. Workbooks case pipeline values map to Case Record Types and case status values map to Case Status picklist values, with custom fields used to align Workbooks status labels to Dynamics status values during migration. Open and resolved cases migrate together; resolved cases retain their resolution notes and closure timestamp.

Workbooks Contract records hold agreement details, related Organisation, start and end dates, and renewal terms. We map these to the Microsoft Dynamics 365 Sales Contract entity if the customer's Sales Enterprise license includes it, or to a custom Contract object with the same fields. Any attached contract documents are downloaded from Workbooks and reattached as Notes or ContentDocument records to the destination contract record. Renewal reminder configuration does not migrate and is documented for the customer's admin to rebuild in Dynamics.