What It Costs to Leave HubSpot or Webflow

The cost to leave HubSpot is not the leftover subscription. It is the hours to export records, rebuild automations, move forms, and prove the dump still maps. Webflow publishes the same kind of list: Webflow's own help, updated 31 October 2025, says CMS, Ecommerce, User Accounts, and localized content are not in the code export. Time a leave drill before you need one.

This is what the vendors' own docs say you can carry out the door, and what you still have to rebuild. If we were sitting with last quarter's invoice, I would run an export, not an argument. Own versus rent AI is the same split: rent the tool, own the files you would still need on Friday.

What HubSpot will give you, in their words

HubSpot's export-records article, last updated 2 April 2026, says you can export records on all products and plans. You get current property values and associations. Download links expire after 30 days. That is a snapshot of the CRM objects you asked for. It is not a running copy of every workflow, every chat, every undocumented sequence in one person's head.

HubSpot's EU Data Act addendum describes a switching process with a two-month notice period after a complete Switching Request. Portable data includes customer data, uploaded materials, transaction records, and customizations where technically feasible. Read that last clause twice. "Where technically feasible" is where the hours hide.

I will not invent a dollar figure for your leave. Count hours. Export contacts. Export deals. Export forms. Rebuild the automations that only lived in the UI. Retell the team which list is true. Put those hours on one page. That page is the cost to leave HubSpot. The leftover months on the invoice are the small line.

What Webflow will give you, in their words

Webflow code export is on paid Workspace plans, not Site plans. The ZIP is HTML, CSS, JavaScript, and assets. The same help article is blunt: CMS, User Accounts, Ecommerce databases, code components, and localized pages are not in that ZIP. Collection lists on the exported site show the empty state. You can export Collections to CSV. Images in that CSV are Webflow-hosted URLs. Those URLs are not your disk.

So you can leave with a static shell and a spreadsheet of items. You cannot leave with a running CMS unless you rebuild it. That is the export table they published. Plan the rebuild hours. Plan the asset copy. Plan the 301s. Who owns the site, the host, and the login is why the registrar still has to be in your name while you do that work.

What the cost to leave HubSpot looks like in hours

Four lines. Export hours. Rebuild hours. Redirect and DNS hours. Teaching the team which list is true. Add a fifth if you have custom code that was never assigned. 17 U.S.C. § 201 still vests copyright in the author unless you have a writing. A paid theme is not an assignment.

Do not skip the associations. HubSpot's export can include associated records, with a default cap you can override. If you export contacts and forget the deals they sit on, you will rebuild the map by memory. Memory is how the first tool you loved becomes the only tool you can use. Open the CSV. Count the columns. If the column you live in is missing, the dump is not done.

Forms and landing pages are their own pile. A record export does not rebuild the form that captured the record. That form is often the only place the field names still match what sales believes. Screenshot the forms before you export. Then you are not guessing later. Same for lists. A list is a query. A CSV is a frozen answer. You need both if you want to leave without a quarter of archaeology.

Run the drill once a year while you are still paying. Export. Time it. Open the files. Click the image URLs. See what 404s. Write the hours. If restore fails, you learned the lease the cheap way. Business continuity architecture is the same drill for the box. This is the drill for the marketing stack.

Lock-in is a default, not a personality flaw

I study behavioral psychology. People keep the first tool they loved because retelling the job feels like starting over. That is the endowment effect I wrote about in the self-hosting decision. The leave drill is how you put a number on the feeling.

Thaler and Sunstein, Nudge, 2008: there is no neutral setup. Staying is the default. Leaving takes a written hour count. Put the hour count on the TCO page next to the subscription. Then you can decide with both eyes open. Know the door either way.

Your business data is yours. At Kief Studio you keep the records, the words, the images, and the tools you paid to own outright. If you want another operator, we pack a dump you can actually open: content, assets, DNS, certificates, a copy you have already seen restored. Switching providers is a business choice. It should not cost you the files you paid to create.

There are two kinds of code. If you pay us to build a tool that you own outright, that tool is yours when you leave. If you ask us to change our platform so it fits how you work, that is still our platform. We run it. It does not become your software. Each project has a license file that names the owner. You can open the folder and see what is yours, what is ours, and what is a library that belongs to someone else. ltfi.ai is the hire. You own the name, the words, the data, and any tool you paid to keep. We hold the night-shift login while you are here. We do not keep your business when you go. kief.dev and briansgagne.com are the engineering notes.

Related reading

• Own versus rent AI
• Who owns the site, the host, and the login
• The endowment effect and the self-hosting decision
• What is included in managed hosting
• Partner vetting questions founders skip
• Self-hosted versus cloud

Frequently Asked Questions

What is the cost to leave HubSpot?

Mostly labor: export hours, rebuild hours, redirects, and teaching the team which list is true. The leftover subscription is the small line. Time an export before you need one.

Can I export my Webflow CMS with the site code?

No. Webflow's help says CMS, Ecommerce, User Accounts, and localized content are not in the code export. Collections can go out as CSV. Plan a rebuild.

Should we leave this year?

I will not answer that without your stack, your labor, and your roadmap. Run the drill. Then you have a number instead of a mood.

Does a CSV count as owning the data?

It counts as a snapshot. Workflows, hosted image URLs, and UI-only automations are still rebuild work. Open the files. Click the URLs.

If I work with Kief Studio, do I keep my data if I leave?

Yes. The records, words, images, and tools you paid to own stay yours. We pack a dump you can open. Wanting another provider is not a penalty.

What counts as custom code?

A tool you pay us to build, and you own it. That is yours. Changing our platform so it works the way your shop works is not custom code. That platform stays ours. The license file in the folder says who owns it. You should not have to ask.

How does this relate to managed hosting?

Hosting is the box. This is the marketing system on top of the box. Own the registrar either way. Drill both.