Migrate from OctopusPro to Pipedrive

OctopusPro Customers map to Pipedrive Person records for individual contacts and Organization records for business entities. When an OctopusPro Customer has a company name, we create both an Organization (the company) and a Person (the primary contact) and link them via the organization_id on Person. Custom fields on the OctopusPro Customer profile migrate to custom fields on the Pipedrive Person. Address, notes, and contact preferences transfer directly.

OctopusPro Bookings are the central record linking customer, field worker, service, time slot, status, and invoice. We map each Booking to a Pipedrive Deal, preserving the service description as the deal title, booking status as pipeline stage, and booking value as deal value. The original Booking ID is stored in a custom field booking_id__c for traceability. Booking notes and custom intake fields migrate to the Deal's activity history and custom field values.

OctopusPro Field Worker records (name, role, contact details, pay rates, location tracking preferences) map to Pipedrive User records. We match by email address. Any OctopusPro Field Worker without a matching Pipedrive User email goes to a reconciliation queue for the customer's admin to provision before the booking migration phase. Field worker location tracking and pay rate fields have no Pipedrive equivalent and are flagged for manual review.

OctopusPro Services (name, description, pricing rules, duration, service-area constraints) map to Pipedrive Product2 records. Service pricing migrates to Product2 standard price, and service duration migrates to a custom field service_duration_minutes__c. Service-area constraints have no Pipedrive equivalent and are noted for admin-level configuration if relevant.

OctopusPro Invoices (line items, tax, totals, payment status, linked to bookings) map to Pipedrive Deals with activity entries. The invoice total migrates as the deal value, and invoice status (paid, unpaid, voided) is preserved in a custom field invoice_status__c. The invoice PDF is stored as an Activity with a document attachment. Pipedrive does not have native invoicing; customers who need full invoice lifecycle management connect an accounting integration post-migration.

OctopusPro Payment records (amount, method, date, status against an invoice) map to Pipedrive Activity records of type note attached to the related Deal. Payment method, amount, and status are stored in custom fields on the activity. Partial payments and refunds are preserved as separate activity entries with payment_type__c distinguishing the transaction type.

OctopusPro Quotes (pre-booking documents with line items, validity dates, and accept/reject status) map to Pipedrive Deals in early pipeline stages. Quote validity dates migrate to custom fields, and the accepted/rejected status is preserved as a deal status label. Pipedrive Smart Docs (Premium and above) can be used for professional quote generation post-migration.

OctopusPro tenant-specific custom fields on Customer profiles (for example, pet health history in vet services or gate codes in field service) map to Pipedrive custom fields on the Person object. Field types are matched: text to string, number to numeric, date to date, checkbox to boolean. OctopusPro Button Group, Radio Button, and Multiple-Select List types map to Pipedrive enum (picklist) fields with corresponding options.

OctopusPro custom fields on Bookings (intake information, structured checklists, field data) map to Pipedrive custom fields on the Deal object. Signature fields are not supported in Pipedrive custom fields; we preserve the signature event as an activity note and flag for reconfiguration in Pipedrive's Smart Docs add-on if the customer has a Premium plan or above.

OctopusPro Forms and checklists capture structured field data at the booking level — job photos, tags, intake information. Schema varies by service type. We map available form fields to a combination of Deal custom fields (for structured data) and Activity notes (for free-text or photo references). The form schema itself does not migrate as a reusable template; we deliver a written form inventory for the customer's admin to recreate in Pipedrive if needed.

OctopusPro Automations define trigger-action workflows for scheduling, notifications, and status changes. We capture automation rules during scoping as a written inventory document with trigger type, conditions, and actions for each active automation. Migration of automation triggers to Pipedrive Workflows is not in scope because Pipedrive Workflows are a different execution model. The customer uses the inventory document to rebuild automations in Pipedrive's Automation section post-migration.

OctopusPro Service-level FAQs are linked to specific services and appear in the customer portal and email templates. FAQ content migrates as Activity notes attached to the relevant Service (Product in Pipedrive). Display configuration and portal settings do not migrate because the Customer Portal is an OctopusPro-specific configuration layer. The migrated FAQ content is available for the customer's admin to repurpose in Pipedrive email templates or knowledge base integrations.