Migrate from Rebrandly to Elido

Rebrandly links use "slashtags" — custom suffixes on branded domains. Elido imports them and maps each Rebrandly domain to an Elido custom domain you control. The process takes under 10 minutes to configure; the background import runs in minutes to an hour depending on link count.

Before you start#

• Your Rebrandly API key (any paid Rebrandly plan exposes the API; free plans may not).
• At least one custom domain configured in Elido if you want to preserve your branded short URLs. Otherwise links land on s.elido.me.

Step 1 — Generate a Rebrandly API key#

1. Log into Rebrandly.
2. Go to Account → API → Create API Key.
3. Give it a name ("Elido import") and copy the key.

Step 2 — Open the migration wizard in Elido#

1. Go to Dashboard → Integrations → Rebrandly Migration, or click Start migration from the integrations page.
2. Paste your Rebrandly API key. Click Connect.
3. Elido lists every Rebrandly workspace attached to your account. Select the ones you want to import.

Step 3 — Map slashtag domains#

Rebrandly links live on custom domains you own (e.g. brand.ly, go.acme.com). For each:

• Map it to an existing Elido custom domain, or
• Map it to a shared Elido domain (s.elido.me for Pro/Business).

Unmapped domains default to s.elido.me.

Step 4 — Choose conflict resolution#

Before running, pick what happens when a slug already exists in your Elido workspace:

• Keep Elido — skip the incoming link, log it.
• Suffix — append -rb to the imported slug, keep both.
• Skip — leave both as-is, log the conflict.

The per-row conflict log is available after import in the Import log tab.

Step 5 — Run the import#

Click Start import. The worker paginates through Rebrandly's GET /v1/links endpoint and creates each link in Elido with:

• Destination URL.
• Slashtag → slug mapping.
• Tags (name-matched or created fresh).
• Creation date.

Large workspaces (5,000+ links) take 5–15 minutes. You'll receive an email when done.

What gets imported#

• Destination URL and slug.
• Tags.
• Link title (if stored in Rebrandly).
• Creation date.

What doesn't migrate#

• Click analytics — Rebrandly's per-click data is not accessible via API export. New clicks start tracking in Elido from cutover.
• Password-protected links — Rebrandly supports passwords on links. Elido also supports this, but passwords aren't exported via the API. Re-add them manually after import if needed.
• UTM presets — Rebrandly has UTM builders saved per link. These aren't importable; recreate them in Elido's link settings.
• Team member assignments — Links become owned by the workspace that runs the import.

Troubleshooting#

"Invalid API key" — Confirm the key with a direct API call:

curl -H "apikey: YOUR_KEY" https://api.rebrandly.com/v1/account

A valid key returns your account info.

Slashtags imported but on wrong domain — Check the domain mapping step. Rebrandly links without a mapped domain fall back to s.elido.me. Re-run the import after correcting the mapping (duplicate rows are skipped; only unmapped ones re-import).

Import shows 0 links after connect — Your Rebrandly workspace may be empty, or the API key belongs to a different account than the one with your links. Verify by calling GET /v1/links directly with the key.

Email not received on completion — Check spam. Sender is [email protected].