Migrate from OctopusPro to Microsoft Dynamics 365 Sales

OctopusPro Customer records map to a Microsoft Dynamics 365 Account as the organizational record and a primary Contact as the point of record. Name, phone, email, address, and notes transfer to Account (company-level) and Contact (individual-level) fields respectively. Customer Portal preferences do not migrate; these are a configuration layer with no data payload in OctopusPro.

OctopusPro Bookings are the central record — they combine a customer link, one or more field workers, a service, a time slot, status, and often an associated invoice. Microsoft Dynamics 365 Sales has no booking or job object natively. We recommend a custom Job entity on Dataverse to capture service name, scheduled date, worker assignment, status, and booking-level custom fields; the commercial dimension (estimated value, service type) maps to Opportunity for pipeline tracking. Historical bookings with invoiced amounts map as closed Opportunities with the invoice amount as the Actual Value.

OctopusPro field worker records (name, role, contact details, pay rate, location tracking preferences) map to Microsoft Dynamics 365 User records. We match by email address. Field-worker-specific attributes such as pay rate are not native Dynamics fields and require custom fields or Notes. GPS tracking and location monitoring settings have no equivalent in Microsoft Dynamics 365 Sales and do not migrate.

OctopusPro Invoice records — line items, tax, totals, and payment status tied to a booking — map to Microsoft Dynamics 365 Sales Invoice (available in Sales Enterprise tier) or to a combination of Order and a custom Invoice entity for Sales Professional. Invoice-to-booking linkage is preserved via the custom Job entity reference. Unpaid invoices migrate with their balance outstanding for follow-up in Dynamics.

Payment records (amount, method, date, status) map to payment records on the corresponding Dynamics Invoice or Order. Partial payments, overpayments, and refunds are flagged as exceptions in the migration report for the customer's admin to reconcile manually in the destination. OctopusPro POS receipts are not migratable as receipt images; we capture the payment data only.

OctopusPro Quotes (line items, validity dates, accept/reject status) map to Microsoft Dynamics 365 Quote records linked to the Account and Opportunity. Quote status (Draft, Sent, Accepted, Rejected, Revised) maps directly to Dynamics Quote Status. Signed or approved quotes with a linked booking are flagged for conversion to a closed Opportunity at migration time.

OctopusPro Service definitions (name, description, pricing rules, duration, service-area constraints) map to Dynamics 365 Product2 records. Pricing rules and duration migrate as custom fields on Product2 or as fields on the associated PricebookEntry. Service-area constraints have no native Dynamics equivalent and require a custom field or a note in the migration inventory.

OctopusPro custom fields on Customer profiles and Bookings are tenant-specific and must be discovered from OctopusPro support as part of the export process. We map each discovered custom field to the corresponding custom field on the target Dynamics entity (Account, Contact, or custom Job entity), using the Dataverse field type that most closely matches the source data type. Custom field schema discovery is completed during the scoping phase before any data transforms are written.

OctopusPro forms and checklists capture structured field data at the booking level — job photos, intake tags, condition reports. We map the captured data fields to custom fields on the Job entity where available; unstructured notes, photo references, and narrative content migrate as Note records linked to the parent record. Form schema and layout do not migrate; the data captured inside them does.