Migrate from OneHash CRM to HubSpot

OneHash's flat contact model routes to HubSpot contacts. If OneHash has a separate lead concept, it maps to HubSpot contacts with a lead-status property. OneHash lifecycle_stage and lead_status values are preserved as HubSpot native lifecycle_stage and a custom lead_status property. The OneHash source ID is stored as a custom Source_ID property for traceability.

OneHash company records map 1:1 to HubSpot companies. OneHash parent-company links map to HubSpot's top-level Parent Company field on the company record. OneHash multi-company contact associations are preserved as HubSpot's primary-company link on the contact, with secondary companies surfaced in the contact's associated companies panel.

OneHash deal records map to HubSpot deals. Deal name, amount, close date, and owner all map directly. OneHash deal stage values map to HubSpot deal stage pick-list values — we create HubSpot stages matching the OneHash stage names. OneHash pipeline name maps to HubSpot's pipeline field on the deal record. Closed-won and closed-lost statuses are preserved with their original timestamps.

OneHash logged calls, emails, meetings, and notes migrate as HubSpot engagements. Call logs map to HubSpot calls, email records map to HubSpot emails, meetings map to HubSpot meetings, and notes map to HubSpot notes. All original timestamps and owner assignments are preserved. HubSpot's engagement timeline on each contact and company record shows the full activity history.

OneHash custom properties on the contact object become HubSpot custom contact properties. Property names are converted to HubSpot naming conventions (typically lowercase with underscores). Field types are matched — text to text, number to number, date to date. OneHash's multi-currency flag, if stored as a contact property, is preserved as a custom text field in HubSpot.

OneHash custom properties on deals map to HubSpot custom deal properties. OneHash's currency_code field (e.g., USD, EUR) is preserved as a custom text property since HubSpot Sales Hub doesn't have a native multi-currency deal field. Amount is stored in the primary HubSpot Amount field; currency code is preserved separately for reconciliation.

OneHash custom properties on companies become HubSpot custom company properties. Industry, employee count, annual revenue, and similar standard fields map directly where OneHash uses them. Any OneHash-specific company fields (e.g., tax ID, billing currency) are created as HubSpot custom text or pick-list properties as appropriate.

OneHash file attachments on records are downloaded and re-uploaded to HubSpot Files. File associations are preserved by linking each file to the original record in HubSpot. HubSpot's file size limits apply (default 25MB per file); files exceeding the limit are flagged before migration for manual handling.

OneHash owner IDs are resolved by matching the owner's email address against HubSpot users. Unmatched owners are flagged before migration — your team either invites them to HubSpot first or assigns their records to a fallback owner. No record lands without a valid HubSpot owner. Original owner names are preserved in a custom Source_Owner_Name field for audit continuity.

OneHash workflow definitions and approval chains do not migrate. They operate at the API level with platform-specific trigger logic that has no HubSpot equivalent. We export your OneHash workflow definitions as a structured JSON document for your HubSpot admin to reference during rebuild. Approval chains should be rebuilt using HubSpot's workflow approval actions or a third-party tool like SalesFlow.