Migrating a CRM isn't a one-day project. Done right, it's a structured switchover that takes 2-4 weeks for most mid-market teams. This guide covers what to expect when moving from HubSpot to OMB Cloud — what data migrates cleanly, what needs manual mapping, and the order that minimizes business risk.
What migrates cleanly
- Contacts. Standard fields (name, email, phone, company association) map 1:1.
- Companies. Including industry, size, location, and custom properties (with field mapping).
- Deals. Pipeline, stage, owner, amount, close date.
- Activities. Notes, calls, emails, tasks.
- Email history. Threads attached to the right contact.
What needs manual mapping
- Custom properties. HubSpot custom fields → OMB Cloud custom fields. Usually a 30-minute mapping session.
- Workflow automation. HubSpot workflows don't translate directly. We rebuild them in OMB Cloud Automations, which is often a simpler model.
- Marketing emails / sequences. If you used HubSpot Marketing Hub, sequences are exported as templates and rebuilt.
- Lists / segments. Definitions are rebuilt with equivalent OMB Cloud filters.
- Integrations. Each integration (Gmail, calendar, etc.) is reconnected via OAuth on the new platform.
The migration order
- Sandbox import. Full data dump into an OMB Cloud sandbox tenant. Validate against HubSpot counts.
- Field mapping review. Walk through custom fields with your team. Adjust mapping.
- Automation rebuild. Recreate the 5-10 workflows that actually run your operation. Skip the dormant ones.
- User training. Two sessions of 90 min. Pipeline, daily workflows, quoting.
- Cutover. One day. HubSpot moves to read-only for 30 days as fallback. New activity logged in OMB Cloud.
- 30-day reconciliation. Compare metrics across the two systems to catch any drift.
Common gotchas
- Email tracking pixel. HubSpot tracks via embedded pixel. OMB Cloud uses a first-party pixel; visit data is more reliable but the format differs.
- Deal stage definitions. Teams often have aspirational stage definitions in HubSpot ("Demo Booked" really means "deal is dead"). Take this chance to rationalize.
- Workflow dependencies. Test in sandbox before cutover. Sometimes a workflow you forgot triggers downstream.
What you keep, what you let go
Keep: data history, pipeline structure (cleaned up), customer-facing email continuity. Let go: HubSpot-specific UI habits, sequences that have run for 18 months without anyone reviewing them. Migration is the natural moment to clean house.
Compare structure at OMB Cloud vs HubSpot.