From Rebrandly

Rebrandly’s pitch is branded links per domain; Elido’s pitch is the same plus EU residency, transparent custom-domain pricing, and plain REST without the workspace-in-header workarounds. The migration is a CSV import plus a per-domain CNAME flip.

Before you start

Rebrandly’s export columns: slashtag, destination, domainName, title, description, tags. The slashtag is the equivalent of Elido’s slug — they import 1:1.

Bulk import

// scripts/import-rebrandly.mjs
import { readFileSync } from "node:fs";
import { parse } from "csv-parse/sync";
 
const WS = 1;
const TOKEN = process.env.ELIDO_TOKEN;
const rows = parse(readFileSync("rebrandly-export.csv"), { columns: true });
 
const chunks = [];
for (let i = 0; i < rows.length; i += 100) chunks.push(rows.slice(i, i + 100));
 
for (const chunk of chunks) {
  const links = chunk.map((r) => ({
    destination_url: r.destination,
    slug: r.slashtag,
    title: r.title,
    description: r.description,
    tags: r.tags, // comma-separated
  }));
 
  const res = await fetch(
    `https://api.elido.app/v1/workspaces/${WS}/links/bulk`,
    {
      method: "POST",
      headers: {
        Authorization: `Bearer ${TOKEN}`,
        "Content-Type": "application/json",
      },
      body: JSON.stringify({ links }),
    }
  );
 
  const body = await res.json();
  console.log(`batch ${chunk.length}: ${body.created} created, ${body.failed?.length ?? 0} failed`);
}

Notes:

• domainName is dropped on import — Elido binds links to a workspace, not a hostname. After cutover (next section), the redirect host is whichever custom domain the workspace owns.
• Slashtag → slug is exact. If a slashtag clashes with an Elido-generated slug, the row fails with slug_taken; rerun those with slug omitted.

Custom domain cutover

Rebrandly routes traffic via CNAME → rebrandlydata.com; Elido uses CNAME → edge.elido.me. Run them in parallel until Elido is verified.

# 1. Add domain in Elido
POST /v1/workspaces/1/domains
{ "hostname": "go.example.com" }

# 2. Verification TXT (Bitly is still serving)
_elido-verify.go.example.com.  TXT  "verify=<token>"

# 3. Flip when status = verified
go.example.com.  CNAME  edge.elido.me.    # was rebrandlydata.com.

# 4. First request issues a Let's Encrypt cert via Caddy on-demand TLS

Wildcard subdomains are supported on Business — register *.example.com and any sub-label resolves through the same cert.

API mapping

Rebrandly puts the API key in apikey header and the workspace ID in workspace. Elido uses Bearer auth and puts the workspace in the URL path.

The Rebrandly slashtag field maps to Elido’s slug. The favourite flag has no equivalent — use tags: "favourite" instead.

Workspaces and roles

Rebrandly has Manager / Member / Viewer; Elido has Owner / Admin / Editor / Viewer. Map them:

Re-invite via the API:

curl -X POST \
  https://api.elido.app/v1/workspaces/1/invitations \
  -H "Authorization: Bearer $ELIDO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "email": "alice@example.com", "role": "editor" }'

The invitee gets an email with a token — the same flow Elido uses for new sign-ups.

Pricing parity

Rebrandly’s free tier is generous on link count but stingy on retention. Elido inverts that trade — fewer links free, but real analytics retention.

After cutover

• Update SDK base URLs in your backend (api.rebrandly.com → api.elido.app).
• Re-issue webhook secrets — Rebrandly’s webhooks are configured per-workspace; Elido’s per-endpoint. Decide whether one Elido endpoint is enough or you want one per integration.
• Archive the Rebrandly account at the end of the billing cycle. Keep the export CSV — it’s your only pre-cutover record.