> For the complete documentation index, see [llms.txt](https://documentation.grax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.grax.com/other/troubleshooting/preparing-grax-for-a-salesforce-org-decommission.md).
# Preparing GRAX for a Salesforce Org Decommission
Your company may have Salesforce orgs that you no longer want to maintain after a consolidation, merger, or business reorganization. GRAX makes it easy to protect this data, search, and reuse it without paying Salesforce to keep the org active.
After disconnecting from Salesforce, the backup of your data remains safe with GRAX and accessible through powerful tools including Global Search.
### Before you Begin
The following must be in place before proceeding with decommissioning:
* GRAX is [connected to Salesforce](https://documentation.grax.com/other/settings/connecting-salesforce) and [storage is configured](https://documentation.grax.com/other/settings/connecting-storage)
* [GRAX Backup](https://documentation.grax.com/protect-data/backup#how-do-i-enable-it) is current. Verify by reviewing the Safe Up To date/time on the Backup Dashboard.
* At least one local GRAX user has been created (see below)
* *(Optional)* Ensure all desired objects are enabled on [Data Lake](https://documentation.grax.com/reuse-data/data-lake)
### **Step 1: Create Local Users**
Once Backup is up to date, the first step prior to decommissioning your Salesforce Org is to create a [local user](https://documentation.grax.com/other/permissions-and-access/local-users) within your GRAX app. This allows simple login access via email and password, as GRAX will no longer have access to Salesforce OAuth to provide authentication.
**Best Practices for Local Users**
* Create at least **two admin users** to prevent lockout scenarios
* Document local user credentials in a secure password manager
* Ensure passwords are set to **never expire** for long-term disconnected deployments
* Optionally, create local users for key stakeholders who may need data access
Once the prerequisites are met and a local user is created, please contact [GRAX Support](https://documentation.grax.com/support/get-support) to verify all is set prior to safely decommissioning your Salesforce Org. GRAX Support will help by giving the green light to this transition and enable **Decommission Mode** for your GRAX app.
### Step 2: Contact GRAX Support
Once your backup is current and local users are created, contact GRAX Support before proceeding. Support will:
* Verify your backup state and local user configuration
* Confirm Data Lake and any other dependencies are in order
* Enable **Decommission Mode** for your GRAX app
{% hint style="warning" %}
Note that any changes to data in the Salesforce org made after disconnecting GRAX will no longer be captured by GRAX Backup. Ensure all desired data has been backed up before proceeding.
{% endhint %}
### Navigating your GRAX app in Decommissioned Mode
Once GRAX is placed in a Decommissioned Mode by GRAX Support, the app operates as a standalone application for accessing historical data. The GRAX app remains largely the same, but features that rely on a live Salesforce connection are disabled.
**Supported Features in Disconnected Mode:**
* [**Global Search**](https://documentation.grax.com/reuse-data/global-search): Search and view historical backed up data
* [**Sandbox Seeding**](https://documentation.grax.com/reuse-data/sandbox-seeding): Seed historical data to a connected Salesforce org (requires additional configuration)
* [**Purge**](https://documentation.grax.com/protect-data/purge): Manage the permanent deletion of data from the GRAX Data Vault
**Features not Supported in Disconnected Mode:**
* Any features requiring Salesforce API access
* Auto Backup
* Archive
* Restore
* Data Lake
{% hint style="info" %}
Data already delivered to your Data Lake remains intact and accessible there. No new data will be sent after decommissioning.
{% endhint %}
**(Optional) Deactivate Salesforce Integration User**
Once you have confirmed Decommission Mode is working as expected and you have successfully logged in with a local user, you may deactivate the GRAX integration user in Salesforce or delete the connected app. This step is not required, but is recommended if you are fully retiring the org.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://documentation.grax.com/other/troubleshooting/preparing-grax-for-a-salesforce-org-decommission.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.