Nobody searches for an alternative to something that is working out. The search usually starts with a renewal invoice, a trial that ended, a plan that quietly capped something, or — worst — a code on a menu or a van that stopped opening anything. So before the feature table, the honest version of this article: a static code needs no migration at all, a printed dynamic code cannot be moved by anyone, and the thing that decides how painful the switch is has nothing to do with the provider you move to. It is what is already printed.

This is a guide to leaving, written by a QR code generator. Where this site's own plans come up, the numbers are the ones on the pricing page and the behaviour is the one the redirect actually implements — both are stated plainly below, and both are things to check about anyone else before the next print run.

First, find out which kind of code is on the wall

Everything follows from one distinction, and it is the one static vs dynamic QR codes explains in full. A static code has your destination address baked into the pattern itself. A dynamic code has a short forwarding address baked in — one on the provider's domain — and the provider's server turns that into your destination on every scan.

You do not need your old account to tell them apart. Scan the printed code with the phone camera and read the address before you tap it — recent phones show it in the banner, which is exactly what how to scan a QR code describes. If the address is your own site, the code is static and this article is short for you. If the address is somebody else's domain followed by a short token, the code is dynamic, and that domain is the one you are thinking of leaving.

Do this for every distinct code you have in the world, not just the ones in the dashboard. The dashboard shows what the account knows about; the wall shows what is printed.

Static codes: there is nothing to migrate

A static code never depended on the generator. The generator drew a picture of an address; the picture is on your flyer; your flyer will keep opening that address after the generator, its company and its domain are all gone. You can close the old account this afternoon and nothing printed changes.

Two small things are worth doing anyway:

Keep the original files. Download the PNG or SVG of every static code before the account closes, if you can. Not because you cannot make another — any generator will make you a code that opens the same address, and it does not need to be pixel-identical to the old one — but because the file you have already printed from is the one you know scans.
Note that the destination is now the whole job. A static code cannot be re-pointed, so if the page it opens ever moves, the fix is on your site (a redirect from the old address to the new one), not in any generator. Where should a QR code point is the case for choosing that address carefully in the first place.

Making a static code is free everywhere, including here — the format is an open standard and what a QR code actually costs goes through why. If all you ever printed was static, the "alternative" you are looking for is any generator that gives you a clean download, and the free tier of most of them, this one included, does.

Dynamic codes: the printed square belongs to the old provider

This is the part no "alternatives" list says clearly, because it is not good news for anyone selling the next subscription. The pattern on your printed dynamic code encodes an address on the old provider's domain. Only a server answering at that domain can turn it into your destination. That means:

No other provider can take the code over. Nobody — not this site, not anyone — can answer for a domain they do not own. A product that offers to "import your dynamic codes" is importing your list of destinations so you can make new codes. It is not, and cannot be, keeping your printed ones alive.
The printed code lives exactly as long as that redirect does. If the old provider deletes it — at the end of a trial, on cancellation, at a cap, or by going out of business — every copy of that code in the world becomes a square that opens an error page or nothing.
The re-pointing you were paying for is also on their side. You can change where an old dynamic code goes only through the old account, only for as long as that account is allowed to.

So for every printed dynamic code you have three options, and they are the only three:

Keep the old account alive until the next reprint. Usually on whatever the cheapest plan is that keeps redirects answering. This is the boring answer and it is the right one for anything expensive to reprint — the packaging run, the vehicle wrap, the sign that needed a permit.
Find out, precisely, what the old provider does on cancel — and test it rather than trust it. Read the terms for the words "redirect", "deactivate" and "trial". Then downgrade or cancel with one unimportant code still printed and scan it the next day, and the day after the billing period ends. Some providers keep redirects alive after cancellation; many do not; some keep them for a grace period and stop. Your own provider's answer is the only one that matters, and a test costs one sticker.
Reprint. The honest cost of leaving a dynamic code is the reprint, not the subscription — the cost post makes the same point from the other direction. Anything cheap to reprint can be reprinted with a new code and moved on the day you choose.

If the old provider is already gone and the codes are already dead, there is no step one or two. Reprint, and use the moment to decide — per placement — whether the replacement needs to be dynamic at all.

The audit that decides your timeline

Do not start by comparing new providers. Start with a list, because the list tells you how long you have to keep paying the old one, and that number is usually the whole decision.

One row per printed placement — not per code, per place the code is printed. For each: which code it is (scan it), static or dynamic (the address tells you), roughly how many copies exist, and what it would cost in money and time to reprint. A menu insert is a row. The same code on a shopfront decal is a different row with a different reprint cost. The van is a row you will not want to fill in.

Then sort by reprint cost, descending. Three things fall out:

The static rows can be crossed off. They move for free, today.
The dynamic rows that are cheap to reprint move whenever you like. Reprint with the new code, throw the old copies away, done.
The dynamic rows that are expensive to reprint set your timeline. The old account stays alive — or you confirm in writing and by test that its redirects survive cancellation — until each of those is naturally reprinted. This might be a month. For packaging it might be a year. That is not a reason not to switch; it is the reason the switch has a schedule instead of a day.

The audit also tends to surface the reason the bill got big in the first place: dynamic codes on things that never needed re-pointing. A code on a wedding table card, a one-night event poster, or a business card that opens a page you control does not need a redirect it will outlive. Next time, those are static, and the dynamic count — and the plan it needs — gets smaller.

Setting up on the new provider before you touch the old one

Whatever you move to, build the new codes first and leave the old account exactly as it is. The order matters because a scan that fails in the gap between the two is a customer you do not get back.

Recreate the destinations, not the codes. Write down where each old code currently points, from the old dashboard or by scanning — the destinations are yours; the short addresses are not. On this site a new dynamic code is made from a destination URL in the dashboard; each one gets its own short address on this domain.
Decide static or dynamic per placement, using the audit, not the plan. Here a static code is free with no signup (one on the Free plan, unlimited from Pro), and dynamic codes are 25 on Pro and unlimited on Business — the exact caps are on the pricing page so that the promise and the enforced number cannot drift.
Name each code after its placement — "front-window decal", "spring menu insert" — because in a year, when something needs re-pointing, the name is how you find it.
Print one of each and scan it on the cheapest phone in the building before the print run. QR code design that still scans covers the four ways a code fails at this step; a logo or a low-contrast colour that was fine on the old provider's preview is the usual culprit.

The cutover: point both codes at the destination, never at each other

There is a tempting shortcut once the new codes exist: re-point each old dynamic code to the new provider's short address, so that anything scanned from an old print goes old redirect → new redirect → destination. Do not do this.

A chain of two redirects has two providers who can break it and two hops of latency on every scan, and it makes the old account more load-bearing, not less — you now depend on it to reach the new one. The right cutover is flat: the old code points at the final destination (as it always did), the new code points at the same final destination, and old prints simply keep working through the old provider until they are replaced. Nothing scanned from any print goes through more than one hop.

When the last expensive placement on the audit has been reprinted with a new code, scan one old copy to confirm nothing you still care about is on it, and cancel the old account. If you cannot be sure — if there are copies of an old code in the world you cannot recall — that is the row that keeps the old account alive, and it is cheaper than the alternative.

What to check about any alternative before the next print run

The feature table is the least useful page on any generator's site for this decision, because it lists what you get and not what happens at the edges. Ask these instead, of every provider including this one, and prefer answers you can test with one code over answers in marketing copy:

What happens to a dynamic code when the plan lapses? The single most important question and the one most tables omit. Here: a printed dynamic code keeps redirecting to whatever destination you last set; what stops on cancellation is the paid tooling — scan analytics and exports. The redirect stops a scan in exactly three cases — the code has been switched off, it has passed an expiry date you set on it, or it asks for a password you put on it — and it applies no plan check. The FAQ puts it as "for as long as the code exists", which is the honest wording; read it as a policy and test it with one code, exactly as you would anywhere else.
What happens when the account is deleted? Different from cancelling. Here, deleting the account permanently removes every code on it — static and dynamic — and their short addresses, and it happens immediately. So if anything is printed, cancel; do not delete.
Whose domain is in the printed code? Always the provider's for a dynamic code. Here it is always createqrcodes.net on every plan; there is no way to put your own domain in the pattern, and the site says so rather than selling it. If a provider offers a custom domain, understand that it moves the dependency to your DNS and their server both — a real feature, but not independence.
Is there a watermark on the download, and on which plans? Here the "Made with" band is on Free and Pro downloads; only Business exports are watermark-free. That is stated on the pricing table because a customer once found it out after printing, and it is the kind of line that is missing from most comparisons.
What are the caps — codes, and scans? Per-code caps are normal (here 1 static on Free, 25 dynamic on Pro, unlimited on Business). Scan caps are the ones to read the fine print for; here there are none on any plan.
Can you export what matters? Two different things: the list of which code points where, so you can leave again later, and the scan data if you rely on it. Here, honestly: there is no one-click export of codes and their destinations yet — the FAQ says so, and the practical advice is to keep that list somewhere outside any provider's system, which is exactly the audit above. Scan data does export: on a paid plan, every scan row to CSV with browser, OS and the UTM values, and the export stops the moment the plan ends, so do it before you cancel, not after.
What are the analytics, really? Totals, a unique-scan estimate, country and device is what this site records, and how to track QR code scans is honest about what a scan count does and does not tell you. A provider promising more is worth asking exactly how.
Are bulk codes dynamic? Often not. Here, codes generated from a CSV are static — each encodes its own fixed address, with no re-pointing and no scan history. Fine for one-address-per-item; not the same thing as a thousand editable codes.
Is there a way back out? A refund window, a plan you can drop to that keeps redirects answering, and a way to download every code image. Here that is a 14-day window on the first paid month if fewer than five dynamic codes were made, the free plan for the first, and a batch download of the images from the dashboard for the third — the refund terms are on the pricing page, and they should be findable on anyone's.

Choosing the plan you are switching to

Take the audit's numbers to the table, not the other way round. Count the placements that genuinely need re-pointing — the ones that will change under a print you cannot cheaply replace — and that is your dynamic count. Everything else is static and free. If the dynamic count is under twenty-five, that is Pro's cap; if it is more, or you need bulk generation, an API or team seats, that is Business. The one-code question — a single static code, no account — is the free path on the homepage, and a lot of people who search for an alternative turn out to have needed exactly that.

Then make the first codes, print one, scan it, and only then cancel anything.

The short version

Scan every printed code and read the address. Your domain: static, nothing to migrate. Their domain: dynamic, and that domain is what you are leaving.
A printed dynamic code cannot be transferred by anyone. Your options are keep the old account until reprint, confirm and test what the old provider does on cancel, or reprint.
Audit by placement, sorted by reprint cost. The expensive dynamic rows set the timeline; the static rows are free today.
Build the new codes first. Point old and new at the same final destination — never chain one redirect through another.
Before any print run, ask every provider what happens on lapse, on deletion, whose domain is in the code, which plans carry a watermark, what the caps are, and what exports. Here: codes keep redirecting after cancel, analytics stop, deletion deletes, always this domain, Free and Pro downloads carry the band, no scan caps, bulk codes are static.
Choose the plan from the dynamic count the audit produced, not from the feature list.