Almost every team evaluating PathKit is already on Branch (or AppsFlyer, or Adjust). The hardest part of switching isn't picking a tool — it's not torching the deep links that already exist in your last six months of emails, ads, and partner integrations. Here's the plan.
Branch exposes CSV download for every link, deep link config, and 90 days of click/install data from the dashboard. Pull it. Keep it.
Set up a PathKit app, point it at the same custom domain or subdomain Branch uses (e.g. go.yourapp.com), and recreate your deep-link paths. PathKit's POST /v1/link is one call per route — scriptable in 50 lines.
Once routes are mirrored, flip the CNAME from Branch's edge to PathKit's. Existing links in the wild — emails, ads, Reddit posts, partner integrations — keep resolving because the path component is the same.
assetlinks.json hosted on your behalfStart with a 14-day trial on a staging subdomain. Run PathKit in parallel with Branch. Only cut over when the attribution numbers match.