GUIDE
Firebase Dynamic Links migration checklist
Use this checklist to identify which Firebase Dynamic Links use cases can move to simple app install routing, and which require native links, deferred deep linking, or attribution tools. For the routing-only boundary, see when Smart Linker is enough; for launch and QR use cases, see the app download link checklist.
Direct answer
Smart Linker can help with simple install-routing replacements, but it is not a Firebase feature-parity claim. Use it when the job is one public URL that routes people to App Store, Google Play, or web fallback.
What to inventory before migration
- Existing links
- Destinations
- QR codes and placements
- Campaign placements
- Web fallback and app dependencies
- Measurement expectations
Migration sequence
1. Inventory links and placements
Collect the Firebase URLs, QR codes, campaign placements, and any fallback targets tied to them.
2. Classify the use case
Separate routing-only cases from deferred deep linking, attribution, or in-app behavior.
3. Create the replacement Smart Links
Replace routing-only cases with one public Smart Link per use case.
4. Test iPhone, Android, desktop, and QR
Verify the new link in the same places the old Firebase link lived.
5. Update placements
Swap the public URL in campaigns, support docs, and offline materials.
6. Keep unsupported use cases documented
Keep old Firebase links live during transition if needed and document anything that still requires another solution.
What Smart Linker can replace
One public URL
Keep one stable link for the campaign or placement instead of juggling separate URLs.
Store and fallback routing
Route iPhone, Android, and desktop visitors to the right destination for their device.
Editable destinations and custom domains
Update the destination later and keep the public URL recognizable in print and digital assets.
QR-ready links
Reuse the same public URL in posters, packaging, booths, or support materials.
Aggregate clicks
Use basic aggregate click visibility without claiming visitor-level analytics or attribution.
Routing-only replacement map
Can move to Smart Linker
- Simple app install routing
- App Store, Google Play, and web fallback routing
- QR-ready public links
- Editable destinations
- Custom domains for trust and recognition
- Aggregate click visibility
Needs another solution
- Deferred deep linking
- Attribution
- SDK measurement
- Postbacks
- App screen opening
- Native app links
What needs another solution
- Deferred deep linking
- Attribution
- SDK measurement
- Postbacks
- In-app screen opening
- Native app links or mobile measurement partner (MMP) workflows
Migration checklist
- Classify each link as routing-only or deeper platform work.
- Replace the routing-only links with one Smart Link per use case.
- Test the new link on iPhone, Android, and desktop before rollout.
- Keep the old links live while you transition if the placement still needs them.
- Document any use cases that require native links or attribution tooling.
- Do not claim parity with Firebase Dynamic Links for features Smart Linker does not support.
Official boundary note
Firebase’s own deprecation FAQ says Dynamic Links is deprecated and scheduled to shut down. This checklist is for migration decisions, not feature parity.
FAQ
Answers are visible on the page, so the migration boundary is easy to scan.
Can Smart Linker replace Firebase Dynamic Links for simple routing?
Yes. Smart Linker can replace Firebase Dynamic Links when the job is one public URL that routes to the App Store, Google Play, or a web fallback.
Does Smart Linker replace deferred deep linking or attribution?
No. Those are different capabilities. Smart Linker is for install routing, editable destinations, QR-ready links, and aggregate clicks.
Do I need an SDK to migrate simple routing links?
No. Smart Linker handles routing at the link level, so no SDK is required for routing.
Should I keep the old Firebase links live during migration?
If you still need them for a transition window, keep the public placements and test the replacement links before cutting over.
What if I need native app links or app-open behavior?
That job belongs to native link setup or another platform, not to Smart Linker’s simple routing model.
Migrate the routing-only links
Keep the simple install-routing cases on one public URL and leave deeper mobile measurement to the tools that provide it.
Create your Smart Link