# Migration guides

> Step-by-step guides for migrating to Grovs from other deep linking platforms.

Source: https://docs.grovs.io/docs/migration-guides

Move to Grovs from another deep linking platform. There are two kinds of migration; use either or both:

- **Link migration (Branch and AppsFlyer).** Point your existing provider subdomain at Grovs so your old links keep working. The links themselves need no code change.
- **SDK migration (Firebase Dynamic Links).** Replace the provider SDK in your app with the Grovs SDK.

To move to a newer Grovs SDK major version, see [Upgrade Guides](https://docs.grovs.io/docs/upgrade-guides).

## Available guides

- **[Migrate from Branch](https://docs.grovs.io/docs/migration-guides/branch):** move your existing Branch subdomain and links to Grovs.
- **[Migrate from AppsFlyer](https://docs.grovs.io/docs/migration-guides/appsflyer):** move your existing AppsFlyer OneLink subdomain and links to Grovs.
- **[Firebase Dynamic Links](https://docs.grovs.io/docs/migration-guides/firebase-dynamic-links):** migrate from Firebase Dynamic Links for iOS and Android.

## How link migration works

For Branch and AppsFlyer, you attach your provider subdomain to Grovs. The first time someone opens a legacy link, Grovs looks it up with your provider credentials, recreates it and redirects. Later clicks come from the cache.

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

The cutover runs in phases: onboard, provision SSL, prepare the app, flip DNS. Traffic only moves when you change DNS.

> **Warning:** Link migration from Branch or AppsFlyer requires an **active paid subscription**. Firebase SDK migration doesn't.
