Tenant (Environment) Name Cannot Be Renamed — New Tenant Required

Android

When you need to change your Esper tenant's subdomain (for example, from ownerdev.esper.cloud to owner.esper.cloud), the rename cannot be done in place — a new tenant must be created and your devices and configuration migrated to it.

Why this happens

Your tenant subdomain is permanently assigned at creation and embedded throughout the Esper platform — in provisioning QR codes, enrollment tokens, API endpoints, and device configurations. Because every enrolled device holds a hard reference to the original subdomain, there is no supported path to reassign or rename it on an existing tenant.

What the migration requires

Migrating to a new tenant is a significant operational undertaking. Before starting, confirm you are prepared to:

Recreate all Blueprints, apps, device groups, compliance policies, certificates, and wallpapers from scratch
Factory reset and re-enroll every device into the new tenant — devices cannot be moved between tenants without a full wipe
Regenerate all provisioning artifacts (QR codes, Zero-Touch configurations, KME or ABM profiles)
Update every API integration and external client to use the new tenant's endpoint
Recreate all service accounts, API keys, and OAuth credentials

Device history, command history, Activity Feed data, and telemetry from the original tenant cannot be transferred and will remain on the original tenant.

Steps to create a new tenant and migrate

Choose and reserve your new subdomain. Contact your Esper Account Manager or Esper Sales to confirm the desired name (for example, ownerprod.esper.cloud) is available and to request provisioning of the new tenant.
Recreate Blueprints in the new tenant. In the new tenant's Esper Console, go to Blueprints → Create Blueprint and rebuild each blueprint manually. Export your existing blueprint settings from the original tenant first so you have a reference during recreation.
Re-upload or re-link all apps. Go to Apps & Configuration → Apps and re-upload all private APKs. Re-approve and link all managed Google Play apps. App version history from the original tenant will not carry over.
Recreate your device group hierarchy. Go to Devices & Groups → Create Group and rebuild your group structure. Group membership cannot be imported — devices will be assigned to groups during re-enrollment.
Recreate any compliance policies, certificates, wallpapers, and other artifacts manually in the new tenant's Esper Console. There is no bulk export or import tool for these items between tenants.
Generate new provisioning artifacts. Create fresh QR codes, enrollment tokens, Zero-Touch configurations, KME profiles, or ABM profiles scoped to the new tenant. Provisioning artifacts from the original tenant will not work in the new tenant.
Factory reset and re-enroll each device. Devices must be wiped and enrolled fresh into the new tenant using your chosen enrollment method (QR code, Zero-Touch, KME, or ABM). Plan a maintenance window appropriate for your fleet size.
Update all API integrations and external clients. Replace the old tenant endpoint (for example, https://ownerdev.esper.cloud/api/) with the new tenant endpoint (for example, https://ownerprod.esper.cloud/api/) in every integration, script, and API client. Recreate all service accounts and API keys in the new tenant under Settings → API Key Management.

Verify: In the new tenant's Esper Console, confirm that re-enrolled devices appear under Devices & Groups with an Active status, that assigned Blueprints show as applied, and that apps install successfully. Allow up to 15 minutes after enrollment for all policies to sync.

If this doesn't resolve it

If your fleet size or operational constraints make a full simultaneous migration impractical, contact Esper Support to discuss a phased migration approach. When reaching out, include:

The original tenant name and desired new tenant name
Approximate number of devices to be migrated
Any enrollment methods in use (Zero-Touch, KME, ABM, QR code)
Any third-party API integrations dependent on the current tenant endpoint

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.