As a customer, when you click "Get Started" to enable Data 360 (formerly Data Cloud), this creates a unique Data 360 Tenant for your Data 360 configuration. This Data 360 Tenant is mapped uniquely to the Sales/Service org where you clicked "Get Started". This is a one to one relationship where an Org can only have one Data 360 tenant assigned as the Home org.
It is not uncommon for your Org to exist but your Data 360 contract expires. When this happens, your Sales/Service Org continues as if nothing changes. Your Data 360 Tenant however enters a deactivation state. For the next 120 days, your account exists as it did up until your contract expires. When 120 days elapse, the Data 360 tenant begins the deletion process and soon after all your Data 360 data and metadata is deleted.
Generally speaking, if you move from the legacy Customer Data Platform License to the Data 360 License, you must migrate users permission sets. If this action takes place when your previous Data 360 Tenant is in the deactivation state (after expiration but before 120 days), the previous Data 360 Tenant will be reactivated when the new contract is signed/upgraded. This is important to consider as your billing model changes from a Profile centric billing model to a consumption model. For example, if you previously had Data Streams running when your contract expired, on renewal they will be reactivated and immediately begin drawing from your allowed Data Services Credits. Consider stopping or deleting any processes prior to letting your contract expire.
The previously used tenant and all its data and setup will be reactivated in the org that it was provisioned in.
If you let your Data 360 Tenant expire, all of the data and metadata gets deleted. The exception to this is your Sales/Service org will always point to this deleted Data 360 Tenant. For this reason, after 120 days if you were to sign up for Data 360 Provisioning, or buy a Data 360 Starter version, your Org would try to reactivate the deleted tenant and fail silently. You can determine if you are impacted by this limitation by following the below steps:
The following will be available within Data 360 tentatively during the week of August 4th, 2025. If your Data 360 Tenant has expired then within Data 360 Setup you will be prompted with information about and steps to complete a clean up of Data 360 metadata and dependancies. By clicking 'View External Dependencies' you will be able to review Data 360 powered features which need to be deactivated and deleted prior to completing the clean up process. Once dependencies have been deleted, a green check mark will display and you will be able to proceed to the next step. Completing the next step will initiate the clean up process. The clean up process can take multiple hours to complete. Once finished, you should return to Data 360 Setup and be prompted to complete the initial setup steps to begin using Data 360.
Note: This applies to all features that build on top of Data 360 as well. For example, Marketing Cloud Growth is powered by Data 360. Agentforce also requires Data 360.
If you don't want Data 360 for any use case, or want to use Data 360 One on an org that previously had Data 360, work with your Account Executive to remove it from your contract. Support cannot assist with these requests.
The following will be available within Data 360 tentatively during the week of August 4th, 2025. If your Data 360 Tenant has expired then within Data 360 Setup you will be prompted with information about and steps to complete a clean up of Data 360 metadata and dependencies. By clicking 'View External Dependencies' you will be able to review Data 360 powered features which need to be deactivated and deleted prior to completing the clean up process. Once dependencies have been deleted, a green check mark will display and you will be able to proceed to the next step. Completing the next step will initiate the clean up process. The clean up process can take multiple hours to complete. Once finished, you should return to Data 360 Setup and be prompted to complete the initial setup steps to begin using Data 360.
NOTE: Salesforce cannot take these steps on your behalf.
003876228

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.