Migrate from Rebrandly to Flyn
Move your branded links from Rebrandly to Flyn with zero downtime on your custom domains
Last updated: April 2026
Pre-Migration Checklist
Complete these steps before starting the migration to ensure a smooth transition.
- 1Export all links from Rebrandly as CSV
- 2Screenshot your current DNS CNAME settings for each branded domain
- 3List all custom domains connected to Rebrandly
- 4Check your Flyn plan supports the number of custom domains you need
- 5Inform stakeholders about the migration timeline
Step 1: Export from Rebrandly
First, export your existing links from Rebrandly so you can import them into Flyn.
Log in to Rebrandly
Go to app.rebrandly.com and sign in to your account.
Go to Workspace settings
Export is done at the workspace level. Go to your Workspace settings, then click Export. Rebrandly will email you a CSV file.
Download the CSV
Download the CSV from the email, it includes destination URL, slashtag (slug), domain, creation date, and tags. Note: Export may require a premium plan. Alternatively, use the Rebrandly API to export links programmatically.
Step 2: Import into Flyn
Upload your exported links into Flyn. The import wizard auto-maps columns and preserves your slugs.
Create a Flyn account
Sign up at flyn.to/signup, free, no credit card required.
Go to Dashboard > Import
Open the import tool from the Flyn dashboard navigation.
Upload the Rebrandly CSV
Flyn recognizes Rebrandly's export format and auto-maps the slashtag, destination, and domain columns.
Review and confirm import
Preview your links, verify slug mappings, and click "Import All" to complete the process.
Step 3: Domain & DNS Migration
Point your custom domain to Flyn so existing short links keep working seamlessly.
Locate your DNS records
Log in to your domain registrar and find the DNS record for your branded domain (e.g., link.yourbrand.com). Rebrandly uses A records for root domains (pointing to 52.72.49.79) or CNAME records for subdomains (pointing to proxies.rebrandlydomain.com).
Replace with a CNAME to Flyn
Remove the existing A record (52.72.49.79) or CNAME (proxies.rebrandlydomain.com) and add a CNAME record pointing to link.flyn.to instead.
Add the domain in Flyn
In Flyn dashboard, go to Settings > Domains > Add Domain. Enter your custom domain and click Verify.
Verify propagation
Wait 5-30 minutes for DNS propagation. Flyn shows a green status indicator once the domain is active.
DNS Record Summary
| Field | Before | After |
|---|---|---|
| Type | A or CNAME | CNAME |
| Host | go (or your subdomain) | go (no change) |
| Target | A → 52.72.49.79 (or CNAME → proxies.rebrandlydomain.com) | link.flyn.to |
What Transfers
Here is what carries over from Rebrandly to Flyn and what needs to be reconfigured.
| Item | Transfers | Notes |
|---|---|---|
| Destination URLs | All long URLs preserved | |
| Slashtags (slugs) | Rebrandly slashtags map to Flyn slugs | |
| Tags | Tag labels carry over to Flyn tags | |
| Custom domains | Remove A record (52.72.49.79) or CNAME (proxies.rebrandlydomain.com) and add CNAME to link.flyn.to | |
| Click analytics | Historical data stays in Rebrandly | |
| UTM parameters | UTMs embedded in destination URLs are preserved | |
| rebrand.ly links | rebrand.ly is Rebrandly-owned, only custom domains migrate |
Post-Migration Verification
After completing the migration, work through this checklist to verify everything is working.
- Test 5-10 sample links to verify correct redirects
- Confirm all custom domains show verified status in Flyn
- Verify new clicks are tracked in Flyn analytics
- Update any Rebrandly API integrations to Flyn's API
- Keep Rebrandly account active for 30 days as fallback
Troubleshooting
Common issues and how to resolve them.
Slashtags not matching after import
Rebrandly uses the term "slashtag" for what Flyn calls "slug." During import, verify the column mapping shows slashtag mapped to the slug field.
Multiple domains not all resolving
Each custom domain needs its own CNAME updated to link.flyn.to. Check each domain individually in your DNS registrar.
Links redirecting to Rebrandly error page
This usually means DNS has not fully propagated. Wait 15-30 minutes. If it persists, verify the CNAME target is exactly link.flyn.to with no trailing period (unless your registrar requires one).
Frequently Asked Questions
How long does migration from Rebrandly take?
The actual link import takes under a minute. DNS propagation for custom domains takes 5-30 minutes. Total migration is typically 5-10 minutes.
Can I migrate multiple branded domains from Rebrandly?
Yes. Flyn Pro supports up to 3 custom domains. Update each domain's CNAME record individually and add each one in the Flyn dashboard.
Will my rebrand.ly links still work?
Yes, links on the rebrand.ly domain continue working through Rebrandly since they own that domain. Only your custom domain links are affected by migration.
Does Flyn support Rebrandly's link scripts feature?
Flyn does not inject scripts into redirect pages. Instead, Flyn offers custom OG metadata, UTM-based campaign tracking, and webhook events for similar functionality.
Is Flyn cheaper than Rebrandly?
Significantly. Rebrandly's Essentials plan costs $13/month for just 250 links per month. Flyn Pro costs $9/month (annual) with unlimited links, A/B testing, and deeper analytics.
Can I test Flyn before fully migrating?
Absolutely. Create a free Flyn account, import a handful of links, and test with a subdomain before switching your main branded domain.
Ready to Migrate from Rebrandly?
Create a free Flyn account and import your links in minutes. No credit card required.