Migrating from Salesforce to Atlas

A 60 to 120-day playbook for moving from Salesforce to Atlas. For teams under 500 employees who have decided the Salesforce footprint is no longer worth the implementation cost.

Phase 0 — Stakeholder alignment (Days 1 to 7)

• Identify the Salesforce administrator.
• Identify the executive sponsor (CFO or COO).
• Map user populations: sales, marketing, service, ops, finance.
• Agree on success criteria: cost savings, AI deployment, adoption metrics, audit-readiness.
• Set and communicate the timeline.

Phase 1 — Inventory (Days 7 to 14)

• Clouds licensed (Sales, Service, Marketing, CMS, Experience, Slack).
• Standard and custom Objects, with row counts.
• All custom fields per object.
• Validation rules.
• Workflow Rules and Process Builder flows.
• Apex triggers and classes (longest migration tail).
• Lightning components.
• Reports and dashboards viewed in last 90 days.
• AppExchange installations.
• Salesforce Inbox / Einstein add-ons.
• Integration users and outbound API consumers.

Most enterprise Salesforce instances have a 40 to 60 percent unused surface.

Phase 2 — Atlas setup (Days 14 to 21)

• Provision Atlas.
• Configure SSO via your existing IdP (Okta, Azure AD, Google).
• Map Salesforce roles to Atlas RBAC scopes.
• Configure MCP Boss approval policies (start strict).
• Configure the LLM provider.
• Connect Outlook or Gmail.
• Configure Atlas Audit retention.
• Connect Microsoft Copilot Studio if applicable.

Phase 3 — Data export and import (Days 21 to 35)

Recommended export order:

1. Accounts (preserve hierarchies).
2. Contacts.
3. Leads (preserve Lead Source).
4. Opportunities (preserve Pipelines, Stages, Forecast Categories).
5. Activities (Tasks and Events).
6. Cases (if Service Cloud in scope).
7. Custom Objects.
8. Attachments and Files.

Per-object notes:

• Accounts → Atlas Accounts. Hierarchies → parent/child relationships.
• Contacts → Atlas Contacts. Roles and account contact roles map cleanly.
• Leads → Atlas Leads. Lead Status maps. Lead Source preserved as custom field.
• Opportunities → Atlas Opportunities. Pipelines one-to-one.
• Activities → Atlas Activities. Tasks → activities of type "task." Events → activities of type "meeting."
• Cases → Atlas Forge Tasks. Case fields → task custom fields.
• Custom Objects → Vibe data tables or custom fields.
• Attachments → Atlas Storage.

Phase 4 — Workflow and Apex migration (Days 35 to 75)

Longest phase.

Mapping rules:

• Workflow Rule sending email on field change → Vibe event trigger → NyLi proposal → approval-gated send.
• Process Builder flow routing leads round-robin → Vibe function on lead creation.
• Apex trigger doing custom validation → Vibe function on entity event.
• Apex trigger calling external API → Atlas MCP tool surface or webhook handler in Vibe.
• Flow that creates child records on status change → Forge task creation triggered by CRM stage change.
• Validation rules → Zod validation via Atlas validation layer.
• Lightning components → Vibe apps.
• AppExchange integrations → check Atlas integration catalog first; rebuild via MCP if needed.

Allocate two engineering weeks per material Apex trigger or class.

Phase 5 — Marketing and Sites (Days 35 to 60, parallel)

• Marketing Cloud journeys → Atlas Marketing campaigns.
• Marketing Cloud lead segments → Atlas saved views.
• Experience Cloud customer portals → Vibe apps with public exposure.
• CMS Cloud websites → Atlas Sites rebuild.
• Email Studio templates → Atlas Comms templates.

Phase 6 — Service Cloud decision (Days 60 to 90)

• Keep Service Cloud for enterprise contact centers; integrate with Atlas via MCP.
• Migrate to Atlas if service is fewer than 50 agents and primarily email/chat (Forge + Comms + Vibe portals handle this).

Phase 7 — Adoption flip (Days 75 to 105)

• Pilot transitions to Atlas as system of record.
• Salesforce becomes read-only.
• Daily NyLi briefs turned on.
• Approval queue review in daily standup.
• Weekly retros review the audit log.

Phase 8 — Full cutover (Days 105 to 120)

• All users transition.
• Salesforce → minimum (Developer org) or fully decommissioned.
• External integrations pointed at Atlas.
• Salesforce domains and CTAs updated.
• Contract canceled at renewal.

Common pitfalls

• Migrating Apex line-by-line. Don't. Retire unused code.
• Service Cloud scope creep. Keep Service Cloud and integrate if needed.
• Losing the Salesforce administrator. Bring them on as Atlas administrator.
• Marketing Cloud rebuild assumed simple. It isn't.