# Move from Bitly, Rebrandly and others

URL: https://qrdx.dev/docs/migrate
Source: https://github.com/qrdxinc/qrdx/blob/main/apps/docs/content/docs/migrate.mdx

Import your short links and dynamic QR codes into QRdx, keep printed codes working, and keep your branded back-halves.

QRdx imports links and dynamic codes from other providers in one go, so you can move without reprinting what's already out there. Every import has the same three steps: pick what to bring, preview it, import it. Use this guide when you have codes at another service and want them editable and tracked in QRdx.

**Plans**

Imports work on every plan, within your plan's active code limit. Keeping the original back-halves needs Pro or Business. See [Plans and limits](https://qrdx.dev/docs/plans-and-limits).

In a hurry? The short task page: [Bring codes from another service](https://qrdx.dev/docs/help/dynamic-codes/import).

## Free help with your move [#free-help-with-your-move]

If you're moving from another QR code provider, we can help:

- **A switch check.** Send one of your old QR links (the short link a printed code opens) to [support@qrdx.dev](mailto:support@qrdx.dev). We reply with the way of switching that fits and its steps: moving your own domain to QRdx with no reprint, pointing your old links at QRdx, or a reprint.
- **Help with a big move.** If you're moving many codes or your own QR domain, we do the move with you: we map your export file and run the import together, and walk you through the DNS change.
- **More time to change your mind.** If you import your codes before your first payment for a paid plan or within 30 days after it, you have 60 days instead of 30 to ask for that payment back. Say which provider you moved from when you ask. It's an offer that may end; the [refund policy](https://qrdx.dev/legal/refunds#money-back-guarantee) has the details.

## How it works [#how-it-works]

Open [Codes](https://qrdx.dev/dashboard?to=codes), then the **⋯** menu → **Import codes** → **From Bitly and other apps**. Two kinds of source:

- **Connected accounts:** Bitly, Rebrandly, Short.io and Uniqode. QRdx lists your links or codes through the provider's API.
- **Export files:** QR Code Generator PRO, Uniqode (Beaconstac), Flowcode, QR TIGER, ME-QR, TinyURL, Hovercode, Scanova, or any CSV with destination URLs.

Nothing changes in your old account during the import itself.

### What an import creates [#what-an-import-creates]

Each link or code becomes a [dynamic QR code](https://qrdx.dev/docs/dynamic-qr-codes) with:

- its destination and title;
- its tags (optional), and a folder such as "Imported from Bitly" (you can rename it or turn it off);
- notes like `Imported from Bitly bit.ly/3AbCdEf on 2026-11-01.` plus the link's original creation date. QRdx sets its own creation date for the new code.

The preview shows how many codes will be created, which tags are new, and what is skipped:

- **Already imported:** links imported before (from any earlier run) are always skipped, so running an import twice never creates duplicates.
- **Same destination exists:** links whose destination already has a QRdx code are skipped by default. Tick the option to import them anyway.
- **Over plan limit:** links that don't fit in your plan's active codes. The preview offers to import the first ones that fit, or to upgrade.
- **Can't import:** missing or invalid destinations, and links that already point to a QRdx short link.

Imports run in batches of 50 with a progress bar. Closing the dialog is safe: open the importer again and the import continues from **Recent imports**. The summary lists created, skipped and failed codes with the reasons.

## From a connected account [#from-a-connected-account]

1. Pick the provider. If it isn't connected yet, connect it right there (sign in, or paste an API key or token). Tokens are stored encrypted, and you can disconnect in [Settings → Integrations](https://qrdx.dev/settings/integrations).
2. Search, filter by domain or tag, and select links. **Select all matching links** takes up to 1,000 links per import; run it again for the rest.
3. Check the preview and click **Import**.

| Provider | Connect with | List links | Keep printed codes working |
| --- | --- | --- | --- |
| Bitly | Sign in, or a generic access token | Yes | Paid Bitly plans only: 5 link redirects a month on Core, 20 on Growth, 110 on Premium |
| Rebrandly | API key | Yes | Within Rebrandly's monthly destination edits: 10 on Essentials, 50 on Professional, 150 on Growth (none on Free) |
| Short.io | API key | Yes, one domain at a time | Yes, on every plan |
| Uniqode | API key (Uniqode's Core plan and above, as an Owner or Admin) | Dynamic website codes only | Yes, while your plan includes the API. Each code uses about two API requests, out of 250,000 a month on Core, 500,000 on Plus and 2 million on Business+ |

Plan limits are the providers' own and change over time. Check their pricing pages.

Uniqode lists only dynamic website codes: its other code types (PDF, vCard Plus, forms and the like) open pages Uniqode hosts, so make those again in QRdx. Your Uniqode API key is in the **API** section of Uniqode's sidebar. If Uniqode doesn't send the links your printed codes open, the import summary says so: download the mapping CSV and replace each code's destination with its new QRdx link in Uniqode.

## Keep printed codes working [#keep-printed-codes-working]

QR codes you printed with another provider encode that provider's short link. After a connected-account import, the summary offers **Keep my printed codes working**:

1. A **dry run** lists every old link and the QRdx link it would point to. Nothing changes yet.
2. Confirm, and QRdx changes each old link's destination to its new QRdx code. Visitors still end up on the same page, and every scan now shows in QRdx analytics. The old provider still sees a click first.
3. **Undo** puts back the original destinations, which QRdx saved with the import.

If the provider refuses (for example a Bitly plan without link redirects left, or a Uniqode plan or role without API access), QRdx stops, says why, and leaves the remaining links unchanged. A single code the provider won't change (a Uniqode code that's no longer a website code, say) is listed with the reason and left as it was. Links skipped because their destination already had a QRdx code point at that existing code. Links whose back-half moves with your own domain (below) aren't changed: after the DNS switch they're the QRdx link.

**Keep the old account for now**

Keep the provider connected until you're sure: undo needs the connection. The old account also has to stay active for its links to keep redirecting.

## Keep the original back-halves [#keep-the-original-back-halves]

On Pro and Business, tick **Keep the original back-halves** in the import preview. Each code then gets its old back-half instead of a random one when QRdx can keep it, so `bit.ly/spring-menu` becomes `qrdx.dev/q/spring-menu`:

- A back-half is kept when it's 3 to 64 letters, digits, `-` or `_`, doesn't start or end with `-` (see [custom back-halves](https://qrdx.dev/docs/dynamic-qr-codes#custom-back-halves)), isn't reserved, and isn't used yet on `qrdx.dev` by any QRdx code (on your own domain, only by your codes there).
- Otherwise the code gets a generated back-half, and the preview shows the change with the reason, for example `spring-menu → Ab3xK9q · Another QRdx code already uses this back-half on qrdx.dev`. The import uses exactly the back-half the preview shows.
- Back-halves are case-sensitive, as at Bitly and Short.io.

Back-halves that can't be kept get a generated one; those links need a reprint or a redirect at the old provider.

## Your own domain (go.yourbrand.com)

If your links use your own domain, you can move that domain to QRdx and keep the back-halves, so `go.yourbrand.com/spring-menu` keeps working after the DNS switch. [Move your QR domain to QRdx](https://qrdx.dev/docs/move-your-qr-domain) has the checks to make first and each provider's link shapes.

1. Add the domain in **Settings** → **Domains** first. It can stay unverified for now: back-halves are then kept on the domain itself, where they only have to be unique among your own codes, and only a few technical words are reserved.
2. In the import preview, tick **Keep the original back-halves** and pick the domain under **Links on**. The preview shows which back-halves are kept.
3. Import. The codes go on the domain and claim their back-halves right away.
4. Point the domain's DNS to QRdx and verify it (see [Custom domains](https://qrdx.dev/docs/custom-domains)). Do this at a quiet time: links on the domain stop working at the old provider as soon as DNS moves, and start working on QRdx once it's verified.

If the domain isn't in QRdx yet when you import, its back-halves are kept on `qrdx.dev` instead (where they must be free across QRdx). After you add and verify the domain, click **Attach codes** in the import summary to move those codes onto it.

## Path aliases

Some providers put more than a back-half in the links on your domain: a prefix such as `/r/`, several parts separated by `/`, or a back-half shorter than 3 characters. Those paths can't be QRdx back-halves, so after the DNS switch they would stop working. A path alias keeps them: the exact old path on your domain opens one of your QRdx codes.

Shapes it covers, among others:

| Provider | Path on your domain |
| --- | --- |
| Flowcode | `/r/<code>` (some codes are a single character) and `/s/<id>/code_batch-1/<id>`; `/p/<id>` too, if your older codes use it |
| Unitag | `/a/<code>` |
| ME-QR | `/l/<slug>` |
| BL.INK | two words, such as `/code-of-conduct/clip` |
| QR Planet | `/object/<id>` |

There are three ways to add one:

- **With an import.** Keep the back-halves on your domain (above). When a link's path can't be a back-half there, the code gets a generated back-half and keeps the old path as an alias. The preview shows both, for example `r/abc → Ab3xK9q` and "Also answers at go.yourbrand.com/r/abc", and the import adds the alias.
- **By hand.** Open a code on your domain, click **Edit**, and add the old path under **Path aliases**: `/r/abc`, or paste the whole old link. The domain has to be verified first. A code can have up to 5 path aliases.
- **With the API.** [Add a path alias](https://qrdx.dev/docs/developers/api/add-code-alias) (`POST /v1/codes/{id}/aliases` with `{ "path": "/r/abc" }`, or the whole old link) follows the same rules and refuses a path with the same reason as the dialog. [List path aliases](https://qrdx.dev/docs/developers/api/list-code-aliases) and [Remove a path alias](https://qrdx.dev/docs/developers/api/delete-code-alias) do the rest. The key needs `codes:write` to add or remove.

How a path alias matches:

- The path has to match exactly, and capitals count: `/r/ABC` and `/r/abc` are different. A `/` at the end doesn't matter.
- The query string doesn't count, as for back-halves: `/r/abc?utm_source=flyer` opens the code at `/r/abc`. Scans and analytics count as for the code's own link, and its password, schedule, scan limit and pause apply.
- On a domain, each path opens one code.
- A path that would fit a back-half (one part of 3 to 64 letters, digits, `-` or `_`) can't be an alias. Give the code that back-half instead.
- QRdx keeps `/api/…`, `/stats/…`, `/q/…`, GS1 Digital Links (`/01/…`) and files such as `/robots.txt` and `/favicon.ico` for itself.
- `/p/<back-half>` is also where QRdx shows hosted pages. An alias there answers only when no hosted page on the domain has that back-half, and QRdx won't add it while one of your codes there has it.
- An alias answers only while its code stays on that domain. A domain's first alias can take a minute to start working.

## From an export file [#from-an-export-file]

1. Get the file (steps below). QRdx reads CSV up to 2 MB and 1,000 rows per run; for an Excel file, save or download it as CSV first.
2. In the importer, pick the provider and upload the file. QRdx recognizes the provider's columns where it can, and you can change the mapping. Only the destination is required; the old short link (or code ID) lets a re-upload skip codes already imported.
3. Preview and import, then use **Copy all new links** or **Download mapping CSV** (old link → new QRdx link).

QRdx can't change codes that live on the provider's own domain. To keep printed codes working, open each old dynamic code in the old provider and set its destination to the new QRdx link from the mapping. The old account has to stay active for those codes to redirect; reprint with the QRdx codes before you cancel. Codes on a domain you own can move with the domain instead, with no reprint: see [Your own domain](#your-own-domain-go-yourbrand-com) above.

### QR Code Generator PRO [#qr-code-generator-pro]

There's no documented export of the code list. Make a spreadsheet with **Name**, **Short URL** and **Destination URL** for each code. To re-point codes: open the code → **Details** → **Edit**, replace the URL and save. For many codes, its bulk update takes a CSV of new URLs for up to 500 codes.

### Uniqode (Beaconstac) [#uniqode-beaconstac]

**QR Codes → Dynamic**, select all, **⋯ → Export**, per organization or folder. The export's columns (QR Code Name, QR Code URL, Destination URL, Labels and others) are recognized. To re-point: open the code → **Edit** → new URL → **Next** → **Save**. On Uniqode's Core plan or above, connect the account instead (see [From a connected account](#from-a-connected-account)) and QRdx re-points the codes for you.

### Flowcode [#flowcode]

Flowcode exports only codes that are in a folder, so move your codes into folders first. Then open the **Folder** section, tick the folders and click **Download URLs**. The CSV's columns (Flowcode Name, Short Links, Scan Destination) are recognized, and so are those of a bulk-create sheet (Flowcode Name, Flowcode Scan URL). To re-point: **Assets** → the code → **Overview** → **Destination** → **Save**.

### QR TIGER [#qr-tiger]

**My Account** → pick a category (for example URL) → **Download QR List**, once per category. To re-point: **My Account → Dashboard → URL** → the campaign → **Edit** → **Save**.

### ME-QR [#me-qr]

There's no export. List Name, QR link and Destination URL for each code. To re-point: edit the code in your ME-QR codes list.

### TinyURL [#tinyurl]

TinyURL lists CSV export on its paid plans. Export your links as CSV, or list Alias and Long URL. Editing a TinyURL destination needs a paid TinyURL plan.

### Hovercode, Scanova and others [#hovercode-scanova-and-others]

Export your codes as CSV from the provider (Hovercode lists CSV exports on its Business plans; Scanova emails a download link), then check the column mapping. Any CSV with a destination column works with **Another provider (CSV)**.

Static QR codes (from goQR.me, QR Code Monkey, Adobe Express and similar tools) encode the destination itself, so they keep working without the tool. Import their destinations from a CSV only if you want editable, tracked codes for new prints.

## From a QR code library [#from-a-qr-code-library]

Libraries render static codes, so nothing needs migrating: codes already printed keep working. To switch the rendering in your app, install `qrdx` and swap the component.

### From qrcode.react [#from-qrcode-react]

```tsx title="Before and after"
// Before
import { QRCodeSVG } from "qrcode.react";

<QRCodeSVG value="https://example.com" size={256} fgColor="#111827" />;

// After
import { QRCodeSVG } from "qrdx";

<QRCodeSVG
  value="https://example.com"
  size={256}
  fgColor="#111827"
  bodyPattern="rounded"
/>;
```

`value`, `size`, `level`, `fgColor`, `bgColor`, `marginSize` (as `margin`) and `imageSettings` carry over; qrdx adds patterns, gradients and templates. See the [API reference](https://qrdx.dev/docs/api-reference).

### From qr-code-styling [#from-qr-code-styling]

```tsx title="Before and after"
// Before
import QRCodeStyling from "qr-code-styling";

const qr = new QRCodeStyling({
  data: "https://example.com",
  width: 256,
  dotsOptions: { type: "rounded", color: "#111827" },
  image: "/logo.png",
});
qr.append(ref.current);

// After
import { QRCodeSVG } from "qrdx";

<QRCodeSVG
  value="https://example.com"
  size={256}
  bodyPattern="rounded"
  fgColor="#111827"
  imageSettings={{ src: "/logo.png", width: 64, height: 64, excavate: true }}
/>;
```

qrdx is a React component, so there's no instance to append: render it like any element. Downloads use the helpers in the [API reference](https://qrdx.dev/docs/api-reference).

## For developers [#for-developers]

To move codes with a script instead, create them with the [codes API](https://qrdx.dev/docs/developers/api/create-codes): up to 1,000 per request on Pro and Business, with `slug` for the back-half you want to keep and an `Idempotency-Key` so a retry never duplicates a batch.

## Related [#related]

- [Bring codes from another service](https://qrdx.dev/docs/help/dynamic-codes/import)
- [Custom domains](https://qrdx.dev/docs/custom-domains): move your branded domain with the links
- [Short links and file pickers](https://qrdx.dev/docs/short-links-and-file-pickers): keep using Bitly, Rebrandly or Short.io for new codes instead
