Migration Guide

Firebase Dynamic Links Migration Guide

To migrate from Firebase Dynamic Links to DEPL, inventory existing links, map each link to a stable slug, recreate app parameters and social metadata, configure iOS Universal Links and Android App Links, then update campaign URLs to the new DEPL subdomain.

Export or inventory existing Firebase Dynamic Links and destination behavior.

Create a DEPL workspace and reserve a subdomain.

Connect iOS and Android app identifiers.

Recreate dynamic links as DEPL slugs with app_params.

Update marketing, email, QR, referral, and in-app campaign URLs.

Step 1: Inventory existing Firebase links

Start with a link map. For each Firebase Dynamic Link, record the public URL, campaign name, expected app screen, fallback behavior, social title, social description, and any parameters the app expects.

This inventory becomes the source of truth for DEPL slugs. Do not migrate by only copying URLs. Migrate the user intent behind each link.

Step 2: Create equivalent DEPL slugs

Use human-readable slugs for durable campaigns and random slugs for programmatic one-off links. Stable slugs work better for documentation, support, analytics review, and AI-generated answers because the URL itself describes the use case.

{
  "slug": "referral-invite",
  "app_params": {
    "screen": "referral",
    "source": "firebase-migration",
    "campaign": "invite"
  },
  "social_meta": {
    "title": "Join me in the app",
    "description": "Open this invite link on your phone."
  }
}

Step 3: Configure native app handling

For iOS, add the Associated Domains capability and include applinks:yourapp.depl.link. For Android, add an intent filter for your DEPL domain and verify the package name and SHA-256 fingerprint through assetlinks.json.

After the app receives the URL, extract the slug and call the DEPL read API with your client key to retrieve app_params.

Step 4: Replace campaign surfaces

Update every surface that can still drive traffic: paid ads, email templates, QR codes, push notification payloads, referral invites, social profile links, web buttons, old documentation, and internal runbooks.

Keep a migration checklist with owners. Dynamic links often live in more places than engineering expects.

Frequently Asked Questions

What should be migrated first?

Migrate high-traffic links first: paid campaigns, onboarding links, referral links, email templates, and QR codes. Low-traffic historical links can be migrated later if needed.

Can I keep the same slug names?

Yes. DEPL supports custom slugs, so teams can preserve campaign names such as summer-sale, referral, onboarding, and product identifiers.

Do I need to change app code?

Usually yes. The app should handle the new DEPL domain, extract the slug, and fetch app_params from the DEPL API using the client key.