- Getting started
- Licensing
- Setup and configuration
- Hosting Model
- Enabling Data Service
- Managing Access
- Tenant Migration and Deletion
- Using Data Service
- Reference
- Examples & Tutorials
Tenant Migration and Deletion
Data Service offers a way to maintain existing tenant data in the following cases:
- license upgrade or downgrade (Tier migration),
- change of the hosting region (Region migration).
The information is preserved by enabling the tenant migration between license tiers or regions.
Discover each case particularities and the procedures that ensure a smooth transition.
Tier migration refers to the transition of your tenant data between different license plans, such as upgrading from Community to Enterprise or Enterprise trial, or vice versa.
As a first impact, the limits within your current license plan change to reflect the upgrade or downgrade. Therefore, you need to adjust your Data Service units to meet the new data and API usage requirements.
Migration schedule
Once UiPath® detects a change within your license tiers (within 24 h), your Data Service tenant is migrated after seven days.
License downgrades
In case of license downgrades, there are two scenarios to consider, based on the consumed data:
- Less than 100MB—you can continue to read or write data to your tenant.
-
More than 100MB—you can no longer write any new data to your tenant, but you continue to have read permissions.
As an Enterprise user you can see what region you are hosted in by opening your Tenant Settings panel.
Region migration refers to the transition of your existing tenant data to another available hosting region.
To move your tenant data to a different region, you need to submit such a request to our support service.
Migration schedule
Once UiPath® support team receives your request on changing the region, you are notified of the scheduled day of the migration.
Rollback
If you can't access your Data Service in the new configuration, you can request to roll-back to the previous environment within 30 days of migration by submitting a support ticket.
The Automation Cloud policy specifies the deletion of inactive Community accounts, if the inactivity period exceeds 90 days.
If a deleted account had Data Service enabled, the associated tenants and the data they hold are also deleted.
Enterprise accounts are not affected by the 90 days inactivity limit. Therefore, all entities and records within Data Service are preserved even if the service becomes inactive or disabled.
For migrated tenants, the old environments are deleted automatically after 45 days.
