Migrate from Workbooks to HubSpot

Workbooks Organisation maps directly to HubSpot Company using Organisation ID as the source key. Organisation hierarchy (parent-child via Parent Organisation field) translates to Parent Company in HubSpot. Multi-branch organisations become a company with child company records or parent-company links, preserving the full corporate structure within HubSpot's company hierarchy model.

Workbooks Person maps directly to HubSpot Contact using Person ID as the source key for deduplication. The Person's primary Organisation resolves to the Contact's primary CompanyId through the organisation mapping. If the Person has no Organisation assignment in Workbooks, the Contact lands in HubSpot with no company association, and this is flagged for review.

Workbooks Opportunity maps to HubSpot Deal using Opportunity ID as the source key. Opportunity stage translates to Deal stage via value mapping defined during the planning phase. The Opportunity's linked Organisation and Person set the Deal's associated Company and Contact records, establishing the deal-to-contact linkage in HubSpot.

Workbooks Opportunity Stage is a pick-list with custom values per business process. Each stage name maps to a corresponding HubSpot Deal Pipeline stage value during configuration. Probability percentages and forecast categories are re-applied based on HubSpot's pipeline stage settings for accurate sales forecasting.

Workbooks Case maps to HubSpot Ticket using Case ID as the source key. Case priority maps to a Ticket custom priority property to preserve support tier information. Case status (Open, Closed, Escalated) translates to a Ticket status pick-list or pipeline stage depending on your HubSpot Service Hub configuration.

Workbooks Quotation has no native HubSpot equivalent, requiring transformation. The quotation header maps to a HubSpot Deal, preserving the quotation reference number. Each quotation line maps to a Deal Line Item with quantity, unit price, and description. Quotation status (Draft, Sent, Accepted, Rejected) maps to a custom Quotation_Status__c pick-list property on the Deal record.

Workbooks activity records map to HubSpot Engagements using the activity ID as source key. Calls map to HubSpot calls, emails to emails, meetings to meetings, and tasks to notes. Original timestamps, owners, and parent-record links (Person, Organisation, Opportunity) are preserved to maintain complete activity history in HubSpot.

Workbooks Contract has renewal dates, terms, and linked parties with no direct HubSpot equivalent. We migrate contract data as a HubSpot custom object if your subscription includes custom objects (Sales Hub Enterprise or Operations Hub Premium). Otherwise, contract data is attached as a PDF on the linked Contact or Company record with renewal-date and terms metadata in custom properties.

Workbooks Invoice (with line items, totals, and payment status) has no HubSpot equivalent, so migration requires workarounds. Invoice data migrates as custom fields on the associated Deal (invoice number, total amount, payment status). The invoice PDF uploads as a file attachment on the Deal or Contact record for document retrieval.

Workbooks custom fields on any object map to HubSpot custom properties on the equivalent object. Custom field type fidelity is preserved: text stays text, number stays number, date stays date, pick-list maps to pick-list, checkbox maps to checkbox. HubSpot Enterprise tiers support custom objects for complex Workbooks custom record types; lower tiers support custom properties on standard objects.

Workbooks file attachments on records re-upload to HubSpot Files using the Files API and are associated to the equivalent HubSpot record. Large files exceeding 30MB require chunked upload via the HubSpot Files API to handle size limits. Inline images embedded in notes are extracted and re-hosted as HubSpot file attachments linked to the parent record.

Workbooks supports one Person belonging to multiple Organisations via junction records, creating many-to-many relationships. HubSpot Contact has one primary CompanyId field. We map the most-recently-modified Organisation link as the Contact's primary company association. Remaining Organisation links surface as secondary HubSpot Company associations through the Company Contacts association object, preserving all relationship data.