Migrate from Branch

Move your existing Branch subdomain and links to Grovs without breaking old links.

When someone opens an old Branch link, Grovs looks it up with your Branch key, recreates it as a Grovs link and redirects to your branded URL. After that first click, Grovs serves it directly.

This moves existing links only. To create new links and capture attribution through Grovs, also add the Grovs SDK.

How it works

flowchart TD
  A[Old Branch link opened]:::evt --> C{Cached?}:::dec
  C -->|No| D[Look up via Branch API]:::proc --> E[Create and cache link]:::proc --> R[301 to branded link]:::done
  C -->|Yes| R

Only the first visitor to an old link triggers the lookup. Later visits come from the cache, with no call to Branch.

Before you start

An active paid subscription. Without one, the dashboard prompts you to upgrade under Settings → Billing.
A custom Branch subdomain you control, such as links.acme.com, with access to its DNS. Links on Branch's shared *.app.link domain can't be migrated: Grovs can only take over a hostname you control.
Your Branch key. See Finding your Branch key.
An updated app build, shipped before you flip DNS.

Ship the new build before you flip DNS. Grovs serves its own Apple App Site Association and Android assetlinks on the migrated host, replacing Branch's. If DNS moves before your app trusts the host, links open the browser instead of your app.

Migrate your Branch hostname

Open Domain settings

Go to Links → Link Settings → Domain and click Migrate from another platform.

Confirm the pre-flight checklist

If your iOS or Android SDK is integrated, confirm each item before you can continue:

iOS: applinks:old.acme.com is in your Associated Domains entitlement, and the build is on the App Store.
Android: your assetlinks.json setup has the SHA-256 cert fingerprint, and the build is shipped.
Your users have had time to update.

Choose Branch and enter your key

Select Branch and enter your Branch key, for example key_live_... or key_test_.... Grovs uses it to look up the original link when an old URL is opened.

Enter the old hostname

Enter the subdomain you're moving, for example old.acme.com. Grovs shows where its DNS points today. Submit it before changing DNS: Grovs provisions SSL first, and traffic only moves once DNS points at Grovs.

Complete the DNS checklist

Add each record at your DNS provider as it appears:

Hostname ownership verified: the ownership TXT record, if shown.
SSL certificate issued: the SSL validation TXT record(s). If an _acme-challenge record exists, replace its value or add another with the same name.
CNAME pointing to Grovs: the CNAME, once SSL is active.

On Cloudflare, set the CNAME to DNS only (gray cloud), not Proxied (orange). A proxied record blocks the certificate and stops links resolving.

Status refreshes as DNS updates. Click Recheck to poll sooner. SSL takes a few minutes to a few hours, and Grovs retries for up to 72 hours. If it doesn't issue, check the TXT record and start over to re-create the challenge.

Test credentials and flip DNS

Click Test to confirm Grovs can reach Branch with your key:

Result	Action
Credentials OK	Ready.
Credentials invalid	Rotate them in Settings → Migration before flipping DNS, or old links stop resolving.
Rate limited or unreachable	Branch is temporarily unavailable. Try again shortly.

Once SSL is active and the test passes, point the old hostname's CNAME at Grovs. Traffic moves as DNS resolvers refresh.

Finding your Branch key

In the Branch dashboard, open Account Settings → Branch Key and copy the key. Use the key_live_... value for production.

Managing and removing

When migration is active, Links → Link Settings → Domain shows Branch, the migrated hostname, and a green Active badge with the last verification time.

Rotate credentials: if your Branch key changes, use Rotate migration credentials in Settings → Migration. Grovs verifies the new key with Branch before saving.
Remove migration: click Remove migration and type the hostname to confirm. This removes the migration source and the legacy hostname from Grovs.

Repoint or retire the hostname's DNS before removing the migration. If DNS still points at Grovs, old links stop resolving. Removal also clears cached mappings: recreated links keep working, but if you re-onboard, each old slug hits Branch again on first click.

Lifecycle and billing

If your subscription lapses, Grovs tears down the migrated hostname and clears the cached mappings. Recovery means re-onboarding with fresh credentials. Keep billing active for as long as you rely on migration.

Last updated 2026-10-27

Was this page helpful?