Firebase Dynamic Links Migration
Migrate from Firebase Dynamic Links to a lighter Smart Link while keeping the public URL stable and the destinations behind it editable.
Create your link
Create a live, editable app link.
Create your linkRouting proof
See how a Firebase migration keeps live links working
Move a live Firebase-era URL to Smart Linker without forcing every public asset to change at once. The public URL can stay stable while the routing behind it changes later.
Visitor route
Why teams migrate
Teams usually look for a Firebase Dynamic Links migration page when a legacy link product is being retired, a marketing stack is being simplified, or existing campaign URLs need a maintained public destination. Smart Linker fits that work when the goal is to keep one public link stable while the destinations behind it can still change later. It is a practical migration story, not a promise of feature parity with a full mobile measurement platform.
What migration looks like in practice
The cleanest migration path is usually to replace the public URL in the assets people actually see first: launch emails, QR codes, support macros, and bio links. Once the public link is stable, the routing behind it can change later without requiring the campaign to be republished from scratch. That gives teams a simpler handoff than a full platform rewrite.
What Smart Linker does and does not do
Smart Linker does route by device, keep the public URL stable, and let you edit the destination behind the link. It does not claim deferred deep linking, attribution SDK behavior, or install attribution. On Pro, teams can also use workspace analytics and per-link analytics in 7d, 30d, and 90d windows with aggregate-only CSV export. That boundary matters in a migration page because the honest replacement is a lightweight routing layer, not a hidden attempt to recreate every legacy feature in a new wrapper.
Best for / Not for
Choose Smart Linker when
- migrating public install links to a lighter, editable routing layer
- keeping a stable URL in live campaigns while changing destinations later
- QR codes, support macros, or email footers need one maintained destination
- no-SDK setup is the cleaner migration path
- operational simplicity matters more than feature parity
Choose a different migration path when
- the migration must preserve deferred deep linking or SDK behavior
- install attribution data or history needs to be carried forward
- the new platform must own in-app routing or app-open orchestration
- a full mobile measurement stack is part of the migration scope
Operational migration examples
A product team can replace an old Firebase link in a launch email and keep using the same public URL while changing the store destinations later. A support team can point help-center articles at one Smart Link instead of asking users which platform they are on first. A marketing team can move a QR code or bio link to a simpler routing setup without rebuilding every public asset around it.
Firebase Dynamic Links migration FAQ
Short answers for teams migrating from Firebase Dynamic Links to a simpler routing layer.
Does Smart Linker replace all Firebase Dynamic Links behavior?
No. Smart Linker handles public app install routing — one link to the App Store, Google Play, and a web fallback — but does not replicate Firebase deferred deep linking, in-app routing, or attribution behavior.
Can I migrate without changing my app code?
Yes. Smart Linker is a public link service. You replace the shared URL in your campaigns, QR assets, and bios; there is nothing to add inside the app itself for this routing use case.
What is the simplest first step for the migration?
Replace the public Firebase URL in your most visible assets — launch emails, QR codes, support macros, and bio links — with one Smart Link. The public URL stays stable and you can update the store destinations behind it later without touching any other distributed assets.
Create your link
Create a live, editable app link.
Create your link