Migrate from OctopusPro to HubSpot

OctopusPro customers map to HubSpot Contacts with a primary Company (Account) assigned. OctopusPro permits customers without a linked company, which become HubSpot Contacts lacking an AccountId. Multi-company associations in OctopusPro translate to Account Contact Relationships in HubSpot, preserving the full network of company connections. When a customer has multiple company links, FlitStack designates the most recently modified association as the primary AccountId and creates additional relationship records for the secondary company links. This preserves relationship data while conforming to HubSpot's contact-account structure. Teams requiring simultaneous multi-company visibility should discuss custom mapping options with FlitStack before migration begins.

OctopusPro custom profile fields (text, numeric, file upload, date types) are recreated as HubSpot Contact properties under Settings > Properties. File attachments migrate as URLs stored in a text property pointing to re-hosted files. All property data types are preserved during migration.

OctopusPro bookings map to HubSpot Deals with the service name as Deal Name, total job value as Amount, and scheduled date as CloseDate. Booking status (Pending, Confirmed, In Progress, Completed, Cancelled) translates to HubSpot pipeline stage values via value mapping. Technician assignment becomes a custom Contact property or Deal property depending on your chosen model.

OctopusPro booking statuses are mapped value-by-value to HubSpot pipeline stages. 'Pending' maps to an early stage, 'Confirmed' to a scheduling stage, 'In Progress' to an active stage, 'Completed' to a closed-won stage, and 'Cancelled' to a closed-lost stage. FlitStack surfaces the mapping plan before migration runs.

Job-specific OctopusPro custom fields (e.g., equipment used, job photos, site conditions) are recreated as HubSpot Deal custom properties. Photos and attachments are re-hosted and links stored as text properties on the Deal record for reference by the sales or service team.

OctopusPro quotes map to HubSpot Deals using the estimate name as Deal Name and the quoted value as Amount. Line items are stored as a JSON-formatted custom property or as Deal notes. Quote status (Draft, Sent, Accepted, Rejected) translates to Deal stage mapping or a custom pick-list field on the Deal.

HubSpot has no native invoice object. OctopusPro invoices are preserved as a custom object (Invoice) in HubSpot Enterprise, linked to the originating Deal via a lookup relationship. For non-Enterprise tiers, invoice data is stored as Deal-level custom properties and notes — your HubSpot admin decides on the final schema.

OctopusPro payment records map to HubSpot as Notes on the associated Deal, capturing payment amount, date, and method. HubSpot's native payments integration (Payments Hub) can be connected post-migration to capture new payments directly within the CRM, but historical payments are reference records only.

OctopusPro staff records are matched to HubSpot Users by email address. If a HubSpot User does not exist for a staff member, FlitStack flags the record before migration — your team can create the User in HubSpot first or assign the staff member's bookings to a fallback owner. Unmatched staff are preserved as a custom Contact property for reference.

OctopusPro service definitions (name, description, price, duration) map directly to HubSpot Products. Products can be linked to Deals as line items, enabling revenue tracking by service type in HubSpot reporting. Service categories in OctopusPro map to Product families or custom properties on the Product record.

OctopusPro forms and checklists attached to bookings have no direct HubSpot equivalent. FlitStack exports form responses as a JSON-formatted custom property on the associated Deal. For ongoing form capture, HubSpot Forms or Operations Hub workflows can replicate the intake logic post-migration.

OctopusPro automations (booking confirmations, reminder sequences, no-show fee triggers) do not migrate. FlitStack exports the automation definitions as a structured reference document so your HubSpot admin can rebuild equivalent workflows in Automation Hub or Sales Hub workflows after migration completes.