---
title: Salesforce Exit: Prove the destination before cutover
description: Build a Salesforce exit business case, map custom dependencies, run Move Big Rocks in Shadow Mode, and verify the cutover.
---

# A controlled exit from Salesforce

Leaving Salesforce is rarely a simple record transfer. Custom objects, automation, permissions, packages, integrations, and institutional workarounds can make the platform part database, part application, and part operating model.

CRM Exit inventories that system, builds the business case, proves MBR with current data in Shadow Mode, and controls the final cutover.

**Primary CTA:** Request a Salesforce Exit Audit

**Secondary CTA:** Build my exit business case

## What the Audit inventories

- Standard and custom objects.
- Fields, formulas, validation, record types, and source IDs.
- Parent/child, lookup, master-detail, and junction relationships.
- Leads, accounts, contacts, opportunities, cases, activities, campaigns, products, and project-specific objects.
- Files, attachments, notes, and content.
- Users, queues, roles, profiles, permission sets, sharing, and ownership.
- Flow, approval processes, assignment/escalation rules, triggers, and Apex.
- Managed/unmanaged packages and package-owned data.
- APIs, middleware, data warehouse, CPQ, billing, marketing, support, and identity integrations.
- Reports, dashboards, forecasts, and downstream source-ID assumptions.
- Sandboxes, release processes, and administrative dependencies.

## Not every Salesforce behavior has a direct equivalent

CRM Exit creates an equivalence matrix:

- preserve as data;
- translate to MBR configuration;
- rebuild as MBR automation or extension;
- retain through another integrated system;
- archive for evidence;
- retire with business approval;
- mark unsupported.

Apex, managed packages, complex sharing models, and bespoke integrations require explicit engineering analysis. They are not promised as automatic translations.

## Salesforce Shadow Mode

MBR is populated while Salesforce remains authoritative. Incremental synchronization respects API limits and durable checkpoints. CRM Exit reconciles records and dependencies while external side effects remain controlled.

The proof dashboard reports coverage, lag, mismatches, exceptions, API consumption, workflow simulations, and cutover criteria.

**CTA:** Explore Shadow Mode

## Salesforce exit economics

The business case should include:

- licences and editions;
- add-on clouds and products;
- sandboxes and environments;
- data/file storage;
- middleware and integration platforms;
- support plans;
- administrators, developers, architects, and consultants;
- release and compliance overhead;
- expected contract growth;
- transition, training, and risk contingency;
- full MBR operating model.

Do not compare Salesforce licence cost with a `$6 droplet`. Compare complete current and future operating costs over a common horizon.

## Cutover design

- Rehearse the final delta before go-live.
- Freeze or strictly control source writes.
- Preserve stable source identifiers.
- Repoint integrations in controlled order.
- Enable destination side effects gradually.
- Validate critical business journeys.
- Maintain read-only Salesforce access or archive according to contract and retention plan.
- Define rollback triggers and decision deadline.

## Salesforce Exit Audit deliverables

- Metadata/data/dependency inventory.
- Export/API/package coverage report.
- Object/relationship mapping strategy.
- Automation and integration equivalence matrix.
- Permission and identity migration approach.
- Three-year business case.
- Risk register.
- Shadow Proof and Verified Exit proposal.

**CTA:** Request a Salesforce Exit Audit

## Frequently asked questions

### Can Salesforce Flow and Apex be moved automatically?

Not safely as a general claim. CRM Exit inventories the business behavior, identifies equivalents, and scopes configuration, extension development, replacement, or retirement.

### Can users test MBR before cutover?

Yes. Shadow Mode exists to give authorized users current destination data while Salesforce remains authoritative.

### Does MBR replace every Salesforce cloud?

No universal claim is made. The Audit determines which customer operations belong in MBR, which remain integrated, and whether MBR is the appropriate destination.

### Can we keep Salesforce as a rollback system?

The project defines a read-only retention/rollback window subject to licence, contract, data-protection, and operational constraints.