Keep the Unsubscribe Links Working: The Obligation That Does Not Leave With HubSpot

A HubSpot unsubscribe link points at a HubSpot path on your own subdomain with a token nobody else can decode. It must work 30 days after the last send.

· Updated November 19, 2026 · 12 min read

Every marketing email HubSpot has ever sent on your behalf ends the same way, with an unsubscribe link and a manage-preferences link. Both are printed on your own subdomain and point at a HubSpot system path, and each carries a token that only HubSpot can read. The day that subdomain stops pointing at HubSpot, or the day the portal closes, every one of those links returns a 404. The emails don’t know that. They’re sitting in inboxes, and some of them will be opened next year.

That’s a legal problem before it’s a cosmetic one. Under CAN-SPAM, the US law on commercial email, an opt-out has to keep working for at least 30 days after the message goes out, you have 10 business days to honor a request, and you can’t make the recipient do anything more than send a reply email or visit a single page. 1 Source 1 Federal Trade Commission, “CAN-SPAM Act: A Compliance Guide for Business,” ftc.gov, August 2023, edited January 2024, read 19 November 2026. In the guide’s words, any opt-out mechanism “must be able to process opt-out requests for at least 30 days after you send your message”, a request must be honored “within 10 business days”, and a sender can’t require “any personally identifying information beyond an email address” or “any step other than sending a reply email or visiting a single page”. Changing email platforms moves your future sending. The obligation stays behind, attached to the mail you’ve already sent.

We worked through this on an exit for a small B2B software company with a lean marketing team. Its HubSpot contract was ending, and on the day we opened the portal, a three-email welcome sequence and a 13-email nurture were still sending. What follows is what the portal held, what the law required of it, and the one-field page that discharges the obligation for as long as the old emails exist.

HubSpot sends marketing mail from a subdomain you delegate to it, something like email.yourcompany.com, and the two links in every footer go to paths on that subdomain, where HubSpot’s servers answer them. On the portal we audited, all 16 emails in the live sequences carried both links, the unsubscribe and the preferences page, and both resolved to HubSpot.

Each link identifies the recipient with a token in the query string. The token is opaque and signed by HubSpot, 2 Definition 2 Opt-out token: the recipient identifier HubSpot appends to its unsubscribe and manage-preferences links. Because it identifies a person, it must be treated as personal data and never logged, stored in a URL, or sent to analytics. and nothing outside HubSpot can turn it back into an email address. Once the subdomain is repointed at your new site, a click on an old link arrives at a server that’s never seen the token and can’t say whose it is. After the portal ends, nobody can.

So two things fail together: the path stops existing, and the identity behind the click stops being knowable. The first is a routing fix. The second shapes everything the replacement page can do.

The people clicking are real

It’s tempting to treat this as a theoretical exposure, because the emails are old, the audience is small and it’s hard to picture anyone clicking.

People do click. On this portal, recipients unsubscribed seven times in two weeks while we were planning the exit, about one every two days, and every one of them used the link in the email. The welcome sequence and the nurture were both still sending. Those seven people got what they asked for because HubSpot was still answering the link. Had the subdomain moved on the wrong day, the same seven clicks a month later would have landed on a 404, and the only option left would have been the spam button.

That button is the actual cost. A complaint is logged against the sending domain, and a new domain in its first weeks of warming has no reputation to absorb it. The company would be building deliverability on a platform it had just moved to while its own old emails taught recipients to report it.

The subdomain was carrying more than the opt-out

The first thing we measured was which host HubSpot’s opt-out links used. Three readings in the portal agreed: the marketing-email subdomain was listed as the primary marketing email domain, all 435 marketing emails had it as their active domain, and every one of the 369 published web versions lived on it.

The portal’s email tracking settings also named it the click-tracking domain. Click tracking was switched on for both HTML and plain text, so every link in every email the portal had ever sent was rewritten through that subdomain to an opaque path that redirects to the real destination. That means every call to action and every link to a blog post or the pricing page, as well as the opt-out. The rewritten path encodes its destination the same way the opt-out token encodes a recipient, in a form only HubSpot can resolve.

The migration plan had the whole site launching on one day, apex and www together, with every HubSpot record repointed at once. Had the email subdomain moved with them, every link in every email already sent would have died at the same moment, and so would every link in the three nurture sends still on the calendar, each reaching up to about 1,063 enrolled contacts. The company would have mailed its own prospects three times with every button broken.

Every link in every email the portal had ever sent was rewritten through one subdomain. Move it on launch day and every call to action in three live sends goes dead.

Once we’d measured it, the ruling was simple. The email subdomain moves last. The site launches on the apex and www, and the email subdomain stays on HubSpot through the final scheduled send. Until then HubSpot keeps honoring its own tokens and recording each opt-out natively, and a final pull of the portal’s suppression state after that last send carries the late opt-outs into the new platform. 3 See also 3 See Dies With the Portal: the portal-level unsubscribe history is readable only from a logged-in session, and it must be loaded into the new platform as suppression before a single subscriber.Read Dies With the Portal: Seven Things a HubSpot Export Will Not Give You Only then is the record repointed, and the new site takes over the old paths.

That ruling leaves two dates to plan around. The first is the last send, the last morning the nurture is scheduled to fire. It isn’t the contract date, because the nurture sends on a fixed weekday and the contract ends on a different one. The second is the legal floor, 30 days after that send. The page outlives the floor by design, because nobody clears a two-year-old newsletter out of their inbox on a schedule, and a one-field page costs nothing to keep.

What the page cannot know, and the one thing it asks

Because the token can’t be decoded, the replacement page can’t know who clicked, so it has to ask. CAN-SPAM allows a sender to ask for an email address and nothing more, and an address is the only identifier the new platform can act on. The page has one field and one button, which unsubscribes that address from the company’s marketing email. The redirect from the old HubSpot path happens before the visitor sees anything, and the token is dropped at that redirect so it never reaches the page’s URL, the analytics tool or a log line.

That last point is a hard requirement, because the token is a recipient identifier. On the new host, the legacy paths should return a 301 to the clean page with the query string removed. That has to happen in code rather than in the host’s redirect rules, because those rules preserve the query string by default and would carry the token straight into the analytics stream.

The page is designed to be served on all four hostnames HubSpot had ever answered for: the apex, www, the email subdomain and a resources subdomain. Doing all four costs nothing and covers whichever host an old email happens to use. Every other path on the email subdomain, which means every old tracked link, should get a 301 to the homepage with the query stripped, because the tracked-link paths can’t be decoded either. HubSpot’s own identity parameters, the ones it appends to every tracked link, are stripped before any analytics event fires.

The design, in plain words

What follows is the specification we wrote for this exit. Read it as a design to copy rather than a report on a finished build, because it was written while the cutover was still under way.

Visitors never get a challenge to solve. The spam gate is a hidden honeypot field and a per-IP rate limit. A bot-check widget is an extra step, and the law doesn’t allow an extra step. The worst abuse an open form invites is someone unsubscribing an address that isn’t theirs, which is harmless and reversible, and a bot that fills the honeypot gets the same success page while nothing is written.

Every outcome gets the same response. Whether the address was on the list, was never on the list, or came from a bot, the visitor sees the same sentence: done, this address will not receive the company’s marketing email. Identical text means the page can’t be used to probe who’s a customer. An address that wasn’t on the list is recorded in the new email platform as unsubscribed anyway, so that no later import or form can subscribe it by accident. The CRM, if it holds the person, gets an opt-in flag set to false with a timestamp and a source naming this page. If it doesn’t hold the person, it’s left alone, because a CRM isn’t a suppression list and the email platform is. 4 Editor's note 4 HubSpot lets a recipient opt out of one subscription type and keep others. The replacement here has a single marketing audience, so the page collapses any opt-out into unsubscribe-from-all. That’s the stricter reading, and it’s the one the law requires to be possible on a single page. Per-topic preferences are a feature of the new platform, not a compliance requirement.

The page works with JavaScript switched off, because a one-page rule is only met if the page works for everyone who reaches it. It says in plain words that transactional mail is unaffected, that the request takes effect immediately, and whom to write to otherwise.

If the write to the email platform fails, the visitor still sees success. The request is committed to a queue the moment it’s submitted, and a failed write sits in a dead-letter view, the queue’s list of failures, and retries. Ten business days is ample room for a retry. The failure to design out is a visitor who sees an error, tries again and gives up.

One-click unsubscribes, the kind a mail client offers from its own interface, are a separate path. 5 Editor's note 5 Mailbox providers also honor a one-click unsubscribe sent as a POST from the mail client, under the List-Unsubscribe-Post header described in RFC 8058. Where HubSpot points that header is visible only in a received email’s full headers, not in the portal. A POST to an old path gets a 200 and a counter, because without a decodable token there’s nobody to unsubscribe, and the response must neither fail nor pretend.

Nobody gets an alert per submission, because an unsubscribe isn’t a lead, and a weekly count is enough.

The obligation that needs a name

The opt-out is the obligation you can discharge in code. There’s a second one you can’t.

Among the portal’s workflows was one that deleted third-party enrichment data on request. Our review of the automation estate gave it one line: this one “is not a feature, it is a GDPR/DSAR obligation”. It doesn’t leave with HubSpot. The company has a live geographic exclusion rule, which means it has non-US contacts, and someone has to be able to receive a deletion request and act on it from the day after cutover, whichever vendor the enrichment data turns out to have come from.

Every other open question in the migration had a shipping default, and this one didn’t. Our architecture notes record it as the single item with no fallback, because it needs a named person to own it. It can’t be a workflow, a form or an agency, and that includes us. It has to be a person at the company whose name is written next to the obligation, with a documented process they can follow without a HubSpot seat.

The 10 business days need a person too, in a smaller way. The page handles the normal case on its own. If the email platform is down for a week, or a request arrives as a reply to an old email instead of through the link, a human has to notice and act inside the window, and the weekly count is where they’ll notice.

Every other open question in the migration had a shipping default, and this one didn’t. It needs a named person to own it.

What you get for doing this once

At the floor, you get a compliance tail handled once, in code, instead of a complaint handled by a lawyer again and again. The ceiling is more interesting.

The opt-out becomes a record the company owns. In HubSpot, consent was a billing flag with a timeline you could read only from a logged-in session. After the move, every unsubscribe carries a timestamp and a source, including the ones that arrive through a two-year-old email next spring. When a customer, an auditor or a regulator asks whether the opt-out mechanism worked on a given date, you can answer with a row instead of a reconstruction.

The sending domain starts clean and stays clean. Nobody reaches for the spam button because an old link was dead, and no reputation goes on an old email’s broken footer. The consent trap that most migrations fall into, re-subscribing people who had opted out, is closed from both ends: the suppression history goes in first, and the late opt-outs have somewhere to land.

The subdomain rule becomes reusable. The email domain moves last, after the last send and after the last suppression pull. It’s a sequencing decision that applies to every HubSpot exit, and knowing it in advance is the difference between a boring launch day and one that mails up to about 1,063 people a set of broken buttons.

The company also ends up with its obligations written down: which link, which host, which page, and who owns deletion requests. None of that was written anywhere in the portal, and all of it exists only because the exit forced the question.

The order of operations

Read the portal before you touch DNS. Find out which subdomain the opt-out links use, whether it’s also the click-tracking domain, and how many emails have it as their active domain. On this portal the answer to the last one was all of them. Have someone forward a received marketing email with full headers, because where the one-click header points isn’t visible anywhere else.

Schedule the email subdomain’s move for after the last scheduled send and after the final suppression re-pull, and put it on the same change list as the rest of the cutover so it doesn’t get forgotten. If a sequence is still running, decide whether to switch it off early or let it finish, because that decision sets the date.

Build the one-field page before the site launches, and serve the old paths on every host HubSpot ever answered for. Strip the query string in code. Test that a click on an old link, with a HubSpot-style token, ends on the clean page with nothing in the URL, and that no analytics event ever carried the token.

If you’re still deciding whether to leave, the data you think you own is the piece to read first, because the opt-out token is a small example of a large pattern. If you’ve decided, the migration guide covers the content, the forms and the CRM, and the renewal calendar sets out what must happen before the contract ends. The unsubscribe page is the item on that calendar that keeps running after it.

Whatever order the rest takes, write a name next to the deletion obligation and keep the page. The 30 days are the legal floor. The emails you’ve already sent will point at HubSpot’s old paths for as long as anyone keeps them.

The research is free. So is the diagnosis. 60 seconds →

Notes & Sources

1Source: Federal Trade Commission, "CAN-SPAM Act: A Compliance Guide for Business," ftc.gov, August 2023, edited January 2024, read 19 November 2026. In the guide's words, any opt-out mechanism "must be able to process opt-out requests for at least 30 days after you send your message", a request must be honored "within 10 business days", and a sender can't require "any personally identifying information beyond an email address" or "any step other than sending a reply email or visiting a single page".
2Definition: Opt-out token: the recipient identifier HubSpot appends to its unsubscribe and manage-preferences links. Because it identifies a person, it must be treated as personal data and never logged, stored in a URL, or sent to analytics.
3See also: See Dies With the Portal: the portal-level unsubscribe history is readable only from a logged-in session, and it must be loaded into the new platform as suppression before a single subscriber.Read Dies With the Portal: Seven Things a HubSpot Export Will Not Give You
4Editor's note: HubSpot lets a recipient opt out of one subscription type and keep others. The replacement here has a single marketing audience, so the page collapses any opt-out into unsubscribe-from-all. That's the stricter reading, and it's the one the law requires to be possible on a single page. Per-topic preferences are a feature of the new platform, not a compliance requirement.
5Editor's note: Mailbox providers also honor a one-click unsubscribe sent as a POST from the mail client, under the List-Unsubscribe-Post header described in RFC 8058. Where HubSpot points that header is visible only in a received email's full headers, not in the portal.

Frequently asked questions

They stop working. Every marketing email HubSpot sends carries unsubscribe and manage-preferences links that point at HubSpot system paths on a subdomain you delegated to HubSpot, and each carries a recipient token only HubSpot can decode. Repoint that subdomain to a new host and those paths return 404; close the portal and nothing can read the token at all. The emails carrying the links are still in inboxes, so the links have to be caught and served by the new site.
The FTC's CAN-SPAM compliance guide says any opt-out mechanism must be able to process requests for at least 30 days after you send the message, and the request must be honored within 10 business days. The sender can't require any personally identifying information beyond an email address, or any step beyond sending a reply email or visiting a single page. The 30 days run from the last send, which on the portal we audited was the final scheduled nurture email, not the contract date.
No. The token in a HubSpot opt-out link is opaque and signed by HubSpot. Nothing outside HubSpot can decode it, and once the portal closes nothing can. So a replacement page can't know who clicked. It has to ask for the email address, which CAN-SPAM expressly permits, and it must drop the token at the redirect so a recipient identifier never lands in a URL, an analytics event or a log.
It carries more than the opt-out. On the portal we audited, the marketing-email subdomain was also HubSpot's click-tracking domain: every link in all 435 marketing emails was rewritten through it to an opaque path that only HubSpot could resolve. Moving it on the site's launch day would have broken every call to action in three nurture sends that were still scheduled, reaching up to about 1,063 enrolled contacts. It moves after the last send and after the final suppression re-pull.
The obligation does, and the workflow doesn't. One portal held a workflow that deleted third-party enrichment data on request. It's a data-subject-rights obligation rather than a feature to rebuild or retire, and it needs a named owner and a documented process from the day after cutover, whichever vendor the data came from. There's no automated fallback for it.

The next analysis lands Sunday. Get the Briefing →

Before the email subdomain moves

Leave HubSpot without leaving a compliance gap

We sequence the DNS, the last send and the suppression pull so no opt-out link ever dies, and we hand you the one-field page that discharges the obligation for good.