Migrating from HubSpot to Atlas

A 45-day playbook for moving from HubSpot to Atlas. Opinionated, sequenced, based on the migrations we've actually shipped.

Phase 0 — Inventory (Days 1 to 3)

Map the surface area before exporting anything.

• HubSpot Hubs licensed (Sales, Marketing, Service, CMS, Operations, Commerce).
• Number of Contacts, Companies, Deals, Tickets, Custom Objects.
• Active properties per object (custom fields).
• Active Workflows and triggers.
• Active Sequences and Lists.
• Email templates and signatures.
• CMS pages (if on CMS Hub).
• Connected apps from the App Marketplace.
• Reports actually used (most are not).
• API integrations writing into HubSpot.

Most HubSpot instances are 30 to 50 percent unused. The migration is also a cleanup.

Phase 1 — Atlas setup (Days 3 to 7)

• Create the Atlas organization.
• Configure SSO if available.
• Invite 3 to 8 pilot users.
• Configure roles and team scopes.
• Connect Outlook or Gmail for the pilot team.
• Configure SMTP for outbound.
• Configure the LLM provider.
• Configure MCP Boss approval policies (start strict).
• Connect ad accounts if Marketing is in scope.
• Connect Google Drive or OneDrive for Knowledge.

Phase 2 — Data import (Days 7 to 14)

Export from HubSpot. Import to Atlas.

Recommended order:

1. Companies → Accounts in Atlas.
2. Contacts.
3. Deals → Opportunities.
4. Activities (calls, emails, meetings, notes).
5. Custom Objects.
6. Lists → Atlas saved views.

Per-object notes:

• Companies / Accounts. Custom properties → custom fields. Owner mapping by email.
• Contacts. Subscription and lifecycle stages → Atlas lifecycle fields.
• Deals. Pipelines preserved. Amount, close date, probability, owner direct.
• Activities. Calls, emails, meetings, notes → Atlas activities.
• Custom Objects. Map to Atlas Vibe data models or to custom fields.

Atlas's CSV importer is idempotent.

Phase 3 — Workflow migration (Days 14 to 28)

HubSpot workflows do not migrate one-to-one. They map to a combination of Atlas Vibe triggers, NyLi approval flows, and MCP Boss policies.

Mapping rules:

• Workflow that sends an email on stage change → event-triggered Vibe app that drafts the email + NyLi approval flow.
• Workflow that creates a task on form submission → Atlas Sites form → CRM lead → automated task creation in Forge.
• Workflow that enriches data on contact creation → registered Atlas Agent with MCP Boss policy.
• Workflow that rotates leads round-robin → Atlas Vibe function on lead creation.
• Workflow that moves deal stage based on email replies → NyLi proposal grounded in the thread + approval gate.

Phase 4 — Sites and Marketing (Days 21 to 35)

• HubSpot landing pages → rebuild in Atlas Sites (manual today; importer on roadmap).
• HubSpot forms → Atlas Sites forms.
• HubSpot email campaigns → Atlas Marketing campaigns with NyLi-drafted content.
• HubSpot blog → Atlas Sites blog (manual content export).
• HubSpot domains → DNS migration in coordination with cutover.

Phase 5 — Adoption flip (Days 28 to 42)

• Pilot team transitions to Atlas as system of record.
• HubSpot becomes read-only.
• Daily NyLi briefs turned on.
• Approval queue review in team's daily standup.
• Identify any HubSpot data still being written into.
• Start full-org rollout after pilot is clean for 14 days.

Phase 6 — Cutover (Days 42 to 60)

• At the next HubSpot renewal: downgrade to HubSpot Free (for legacy reference) or fully cancel.
• Update external HubSpot links to Atlas equivalents.
• Inform integrations of new system of record.
• Decommission the HubSpot domain.

Common pitfalls

• Importing dirty data. Allocate a day for dedup and cleanup before import.
• Trying to migrate everything at once. The pilot team is essential.
• Re-creating every HubSpot workflow. Many are not used.
• Underestimating CMS rebuild. Treat as its own track.
• Losing internal stakeholders. Bring leadership in early.

Migration support

Atlas's customer engineering team handles migrations on Business and Enterprise tiers. Growth-tier customers use this playbook and ask questions via in-app chat.