Migration Guides
Step-by-step guides for migrating to Grovs from other deep linking platforms.
Overview
Moving to Grovs from another deep-linking platform is straightforward. There are two kinds of migration, and you can 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.
Available guides
- Migrate from Branch: move your existing Branch subdomain and links to Grovs.
- Migrate from AppsFlyer: move your existing AppsFlyer OneLink subdomain and links to Grovs.
- Firebase Dynamic Links: migrate from Firebase Dynamic Links for iOS and Android.
How link migration works
For Branch and AppsFlyer, you attach your existing provider subdomain to Grovs. Old links resolve on demand: the first time someone opens a legacy link, Grovs looks it up with your provider credentials, recreates the matching Grovs link, and redirects. Subsequent clicks are served from cache.
The cutover happens in clear phases, and traffic only moves once you change DNS:
Link migration from Branch or AppsFlyer requires an active paid subscription. Firebase SDK migration does not. See each guide for details.