Migrate from Orderry to HubSpot

Orderry clients are person-centric records with company data embedded. We split them into HubSpot contacts (the named person) and HubSpot companies (the organization), linked by the contact-to-company association. Phone, email, address, and notes migrate to contact; company name, industry, and website migrate to company.

Orderry assets (serialized equipment, repair history, location data) have no native equivalent in HubSpot. We create a HubSpot custom object named Orderry_Asset__c with fields for serial number, asset type, linked contact, linked company, purchase date, and a service history note. The custom object is associated to the matching HubSpot contact or company.

Orderry work orders carry both service-status data and billable line items. We split them: operational work-order records (status, technician, timestamps, asset link) migrate as HubSpot tickets. Work orders with billable products or services and a revenue amount migrate as HubSpot deals with line items. Clients choose the split rule based on whether they track field service separately from sales.

Orderry estimates contain line items, totals, and approval status. These map directly to HubSpot deals, with the deal name referencing the original estimate number and the deal amount reflecting the estimate total. The deal stage reflects the current approval status from Orderry (Draft, Sent, Approved, Declined) and maps to the corresponding stage in your HubSpot deal pipeline. This allows your sales team to continue working from a complete proposal history without re-entering data.

HubSpot does not have a native invoice object. We create Orderry_Invoice__c as a custom object storing invoice number, date, total, balance due, payment status, and a link to the associated contact and deal. Payment records from Orderry migrate as notes on the invoice custom object.

Orderry products with SKU, price, description, and stock quantity map directly to HubSpot products. Stock-on-hand is informational only in HubSpot — inventory levels below zero or out-of-stock flags can be stored as a custom property for reference. This preserves your product catalog structure while acknowledging HubSpot's inventory limitations.

Orderry warehouse stock levels map to HubSpot product custom properties including stock_quantity, reorder_point, and warehouse_location fields. Multiple warehouses in Orderry consolidate into a single stock record in HubSpot unless you require per-location tracking, which can be achieved using custom properties for each warehouse location.

Orderry employee records (name, email, phone, role, clock-in/out timestamps) resolve to HubSpot user accounts by matching email addresses. Only employees with an active HubSpot user account receive a direct user mapping. Unresolvable employees are flagged for administrative review before migration to prevent orphaned records.

Orderry client notes and communication history migrate as HubSpot contact timeline activities with type: note, preserving original timestamps and the creating employee's name as the activity owner. Email and SMS communications from Orderry migrate as engagement records on the contact timeline for full conversation continuity.

Orderry custom fields on any object map to HubSpot custom properties on the corresponding object or custom object. HubSpot property names use snake_case internally; we preserve the original field label as the property name and add the Orderry field ID as a reference note for audit purposes.