Migrate from OctopusPro to Nutshell

OctopusPro Customer records map directly to Nutshell Contact. Standard fields (name, phone, email, address, notes) transfer via the Nutshell JSON-RPC API. If the customer operates a business-to-business model with multiple Contacts per company, we also create a Nutshell Account and link Contacts to it using the Customer's primary address domain as the Account name. Custom fields on Customer profiles (e.g., pet health history, gate codes, vertical-specific properties) migrate to Nutshell custom fields on Contact, but note that Nutshell's API does not support searching by custom field value, so these are flag fields rather than lookup keys.

OctopusPro Bookings are the core linking object — they connect a Customer, a Field Worker, a Service, a time slot, a status, and optionally an Invoice. Nutshell has no booking object. We decompose each Booking into: a Note on the Contact capturing booking details (service name, date, time slot, status, assigned field worker, notes), a custom Contact field booking_status__c for current active bookings, and a Tag on the Contact using the service name for filtering. Booking status history is preserved as separate chronological Notes if the customer requires an audit trail.

OctopusPro Field Worker records (name, role, contact details, pay rates, location tracking preferences) map to Nutshell User accounts. We resolve Field Workers by email match against the Nutshell User table. Field workers who are not Nutshell users (e.g., subcontractors who should not have CRM access) are mapped to Contact records with a role tag field worker__c rather than a User account.

OctopusPro Invoices (line items, tax, totals, payment status) linked to Bookings have no native Nutshell equivalent. We migrate each Invoice as a structured Note attached to the linked Contact, with a header row format: INVOICE | InvoiceNumber | Date | Amount | Status | BalanceDue. Payment records linked to the Invoice append as PAYMENT rows within the same Note block. This preserves the financial record against the customer but is not a queryable financial object in Nutshell.

Payments (amount, method, date, status, reference) migrate as PAYMENT rows appended to the structured Invoice Note on the Contact. Partial payments and refunds are noted with separate rows. Full financial reconciliation requires the customer to maintain OctopusPro's export as the authoritative financial record post-migration.

OctopusPro Quotes (line items, validity dates, accept/reject status) map to Nutshell Opportunity records. The Quote total maps to the Opportunity amount field. Status mapping: draft → Prospecting, sent → Presentation/Proposal, accepted → Won (or the equivalent stage in the customer's Nutshell pipeline), rejected → Lost. Quote validity dates migrate as a custom Opportunity field quote_valid_until__c.

OctopusPro Service definitions (name, description, pricing rules, duration) map to Nutshell Products if the customer uses Nutshell's Opportunity-based quoting. Services without pricing rules migrate as Products with a $0 list price. Service duration migrates as a custom field service_duration_minutes__c on the Product. We create Products before Opportunities so that line items reference the correct Product2 ID during import.

OctopusPro Forms and field checklists capture structured data (job photos, tags, intake information) attached to Bookings. Schema varies by service type. We migrate available checklist fields as a Note attached to the Contact, using a key-value format. Schema varies by service; we flag any fields that require a Nutshell custom field creation and defer those until the custom field is provisioned in the destination.