---
title: Design Manager Serverless Functions Are Going Away. What Now?
description: "HubSpot is shutting down serverless functions built in Design Manager: what is changing, how to check whom it affects & what the migration looks like in practice."
image: https://www.growpoland.pl/hubfs/hubspot-serverless.jpg
---

[![grow-logo-white-transparent](https://www.growpoland.pl/hubfs/grow-logo-white-transparent.png) ![grow\_logo](https://www.growpoland.pl/hubfs/grow_logo.png)](https://www.growpoland.pl/en/) [DEMO HubSpot](https://www.growpoland.pl/en/demo-hubspot) [DEMO](https://www.growpoland.pl/en/demo-hubspot)

- [HubSpot](https://www.growpoland.pl/en/hubspot) 
    - [HubSpot Solutions Partner](https://www.growpoland.pl/en/hubspot/hubspot-partner)
    - [Discover HubSpot's Possibilities](https://www.growpoland.pl/en/hubspot/discover-the-possibilities-of-hubspot) 
          - [HubSpot Sales Hub](https://www.growpoland.pl/en/hubspot/hubspot-sales-hub)
          - [HubSpot Marketing Hub](https://www.growpoland.pl/en/hubspot/hubspot-marketing-hub)
          - [HubSpot Service Hub](https://www.growpoland.pl/en/hubspot/hubspot-serivce-hub)
          - [HubSpot Content Hub](https://www.growpoland.pl/en/hubspot/hubspot-content-hub)
          - [HubSpot Data Hub](https://www.growpoland.pl/en/hubspot/hubspot-operations-hub)
          - [HubSpot Revenue Hub](https://www.growpoland.pl/en/hubspot/hubspot-commerce-hub)
    - [HubSpot Implementation Services](https://www.growpoland.pl/en/hubspot/implementation)
    - [HubSpot Onboarding Services](https://www.growpoland.pl/en/hubspot/onboarding)
    - [HubSpot Web Development](https://www.growpoland.pl/en/hubspot/hubspot-web-development) 
          - [Website on HubSpot](https://www.growpoland.pl/en/hubspot/website-on-hubspot)
          - [UI/UX Design for HubSpot](https://www.growpoland.pl/en/hubspot/ui-ux)
          - [Migration to the HubSpot](https://www.growpoland.pl/en/hubspot/migration)
          - [SEO & AEO in HubSpot](https://www.growpoland.pl/en/hubspot/hubspot-web-development/hubspot-seo-aeo)
    - [HubSpot White Label Partner Agency](https://www.growpoland.pl/en/hubspot/white-label)
    - [HubSpot for Your Business](https://www.growpoland.pl/en/hubspot/hubspot-for-your-business) 
          - [HubSpot for Travel Agencies](https://www.growpoland.pl/en/hubspot/hubspot-for-your-business/hubspot-for-travel-agency)
          - [HubSpot for Manufacturing](https://www.growpoland.pl/en/hubspot/hubspot-for-your-business/hubspot-for-manufacturing)
          - [HubSpot for Hotels](https://www.growpoland.pl/en/hubspot/hubspot-for-your-business/hubspot-for-hotels)
    - Tools 
          - [Website Grader](https://www.growpoland.pl/en/website-grader)
          - [Calculator ROI](https://www.growpoland.pl/en/calculator-roi)
    - [Grow in HubSpot Marketplace](https://www.growpoland.pl/en/hubspot/marketplace/)
- [Eloqua](https://www.growpoland.pl/en/eloqua)
- [Marketing](https://www.growpoland.pl/en/marketing) 
    - [Discover digital marketing](https://www.growpoland.pl/en/marketing/discover-digital-marketing)
    - [Digital strategy & consulting](https://www.growpoland.pl/en/marketing/digital-strategy-and-consulting)
    - [Social media](https://www.growpoland.pl/en/marketing/social-media-marketing)
    - [Branding & Identity](https://www.growpoland.pl/en/marketing/branding-and-identity)
    - [Content marketing](https://www.growpoland.pl/en/marketing/content-marketing)
    - [Copywriting](https://www.growpoland.pl/en/marketing/copywriting)
    - [Martech](https://www.growpoland.pl/en/martech)
    - [Marketing for Manufacturing](https://www.growpoland.pl/en/marketing/marketing-for-manufacturing)
- Knowledge Base 
    - [Blog](https://www.growpoland.pl/en/blog)
    - [CRM](https://www.growpoland.pl/en/knowledge/crm)
    - [HubSpot](https://www.growpoland.pl/en/knowledge/hubspot)
    - [Social Media Marketing](https://www.growpoland.pl/en/knowledge/smm)
    - [Marketing Automation](https://www.growpoland.pl/en/knowledge/marketing-automation)
    - [Content Marketing](https://www.growpoland.pl/en/knowledge/content-marketing)
    - [Lead Generation](https://www.growpoland.pl/en/knowledge/lead-generation)
- About 
    - [Team](https://www.growpoland.pl/en/team)
    - [Portfolio](https://www.growpoland.pl/en/portfolio) 
          - [Dalmec Success Story](https://www.growpoland.pl/en/portfolio/dalmec)

Contact

[PL](https://www.growpoland.pl/blog/funkcje-serverless-w-design-managerze-znikaja)

[![HERO\_SOCIAL\_linkedin](https://www.growpoland.pl/hubfs/HERO_SOCIAL_linkedin.svg)](https://pl.linkedin.com/company/grow-poland) [![HERO\_SOCIAL\_facebook](https://www.growpoland.pl/hubfs/HERO_SOCIAL_facebook.svg)](https://pl-pl.facebook.com/growpoland/) [![HERO\_SOCIAL\_twitter](https://www.growpoland.pl/hubfs/HERO_SOCIAL_twitter.svg)](https://twitter.com/growpoland)

[WebDevelopment](https://www.growpoland.pl/en/blog/tag/webdevelopment)

# Design Manager Serverless Functions Are Going Away. What Now?

 Max Vorozhtsov 

 22 min

 19 November 2026

[WebDevelopment](https://www.growpoland.pl/en/blog/tag/webdevelopment) [HubSpot CMS](https://www.growpoland.pl/en/blog/tag/hubspot-cms)

It all started with a security email. In early November, HubSpot wrote to everyone who owns serverless functions: a vulnerability in Node.js (a flaw in Brotli decompression, CVE-2026-111497) can let an attacker run code remotely, and functions running on Node.js 18 or 20 will never get a fix. HubSpot added that it had no evidence of exploitation, but recommended disabling affected functions and rotating their secrets as a precaution.

The conclusion was obvious: move to a newer Node.js. The catch is that Design Manager doesn't offer anything newer than Node.js 20. So the only way forward is developer projects. To be fair, one of our clients actually panicked (just a little bit). But their questions were pretty reasonable: "Why are serverless functions that have worked fine for almost two years suddenly not good enough? And what even is this developer platform?" It also turned out they had no idea a HubSpot website could involve anything beyond Design Manager.

**The short answer: HubSpot is shutting down serverless functions built in Design Manager, and on February 1, 2027 they stop working**. You don't need to panic. But you also can't leave it until the last week of January. In this article I'll explain what is changing, how to check whether it affects you, what the migration looks like in practice, and what we ran into while moving our clients' functions. Including the parts HubSpot's announcement doesn't mention.

1. [What’s happening and when](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#whats-happening-and-when)
2. [Does this affect you?](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#does-this-affect-you)
3. [“Wait, there’s something besides Design Manager?”](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#something-besides-design-manager)
4. [How the migration works](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#how-the-migration-works)
5. [What actually gets better](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#what-actually-gets-better)
6. [What hurts](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#what-hurts)
7. [Can AI do it for you?](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#can-ai-do-it-for-you)
8. [Also affected: workflow custom code actions and older projects](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#also-affected)
9. [Your checklist before February 1, 2027](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#checklist-before-february-1)
10. [FAQ](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#faq)
11. [Sources](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#sources)
12. [Need any help?](https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#need-any-help)

## What’s happening and when

HubSpot announced the sunset on November 3, 2026, in three stages ([HubSpot Developer Changelog](https://developers.hubspot.com/changelog/sunsetting-design-manager-serverless-functions-and-older-node.js-runtimes-for-custom-code-actions)):

| Date | What changes |
| --- | --- |
| November 3, 2026 | You can no longer create new serverless functions in Design Manager |
| November 17, 2026 | You can no longer edit existing functions. They still run |
| February 1, 2027 | Functions stop running. Requests to `/_hcms/api/` fail |

The reason is the runtime. Design Manager functions run on Node.js 18 or 20, which no longer get security updates, and HubSpot can't upgrade them in place. Functions in developer projects run on Node.js 24 and get updates automatically.

One important clarification, because I've seen a lot of confusion here: your existing functions keep working until February 1. What you lose now is the ability to change them. So if a function has a bug, you can't fix it in Design Manager anymore, and that alone is a good reason to migrate sooner rather than later.

### Also on the clock: legacy HubSpot API versions

If your functions call HubSpot APIs, there's a second deadline to keep in mind. In spring 2026 HubSpot switched to date-based API versions (like `/2026-09/`), and the old numbered versions are going unsupported ([HubSpot Developer Changelog](https://developers.hubspot.com/changelog/legacy-apis-and-legacy-apps-whats-going-unsupported-and-when)):

| API version | Unsupported from |
| --- | --- |
| v4 (e.g. `/crm/v4/`) | March 30, 2027 |
| v1, v2, v3 | September 2027 (exact day not announced yet) |

And no, that's not a typo: the newest version, v4, loses support **six months earlier** than the older v1 to v3.

"Unsupported" means no more bug fixes, reliability improvements or security updates, not that the endpoints switch off on that day. But it also means no new features: everything new will ship only in the date-based versions. Given how fast HubSpot is moving right now, staying on legacy APIs means slowly falling behind, even if nothing breaks. Still, if you're rewriting your functions anyway, it's the perfect moment to move their API calls to the current date-based version too. Do it as a separate step after the migration, so you can tell which change broke what.

## Does this affect you?

The quickest check: look for HubSpot's security email. HubSpot sent it to every account with affected serverless functions, and a separate one to accounts with workflow custom code actions. But it goes only to the primary contact, security contact or Super Admins, so the person who actually maintains your website may never have seen it. Ask around before you assume you're fine.

Beyond the email, the simplest filter: serverless functions require Content Hub Enterprise. If you don't have it, you have no Design Manager serverless functions and you can stop reading here (but check the section about workflow custom code actions below).

If you do have Content Hub Enterprise, look for these signs:

- Your website has custom logic that doesn't come from a standard HubSpot feature: a form that sends data somewhere other than HubSpot, a booking or pricing widget.
- Your site calls an external API (a CRM other than HubSpot, an ERP, a payment provider) directly from a page.
- In Design Manager you see folders ending with `.functions` containing a `serverless.json` file.
- Your templates, modules or JavaScript contain URLs starting with `/_hcms/api/`.

If you're not sure, ask your developer or HubSpot partner. It usually takes them a few minutes to check.

## “Wait, there’s something besides Design Manager?”

Yes, and this is the real story behind the migration. For years, most HubSpot websites lived entirely in Design Manager: templates, modules, CSS, JavaScript, and, for Enterprise accounts, serverless functions. You could do everything in the browser.

Alongside it, HubSpot has been building the developer platform: **developer projects**, managed with the **HubSpot CLI** from your terminal. A project is a folder of code on your computer (ideally in Git) that you upload and deploy as one unit. It has versions, builds and rollbacks, like a normal software project.

Templates and modules still live in Design Manager for now. But anything that runs code on the server now needs a project, a terminal and a deploy process. That's actually the answer to "why did serverless suddenly stop being good enough?": the functions didn't change, the platform under them did. (What this means for your team, I'll cover in "What hurts" below.)

## How the migration works

HubSpot can't migrate your functions automatically, because every function and every page that calls it is unique. The good news: for most sites, you only move the functions themselves. Templates and modules stay where they are, and you change just one thing in them, the URL prefix.

The process looks like this:

1. **Find everything.** List every function, its endpoint, and every template, module, page and setting that calls it. This is the hardest part (more on that below).
2. **Back up.** Download your Design Manager files with the CLI, so you have a copy of what's live today.
3. **Create a project** on the current platform version (`2026.09` at the time of writing). HubSpot generates the project structure for you.
4. **Move each function.** Copy the code, add a small config file per function with its path and method (HubSpot creates an example config file when you create the project, and all its fields are described in the [serverless functions reference](https://developers.hubspot.com/docs/apps/developer-platform/add-features/serverless-functions/reference)), and switch from the old callback style to a modern `async` function. Keep the same path, so `/_hcms/api/events/update` becomes `/hs/serverless/events/update`.
5. **Test the new endpoint** directly and compare its response with the old one.
6. **Switch the callers** one function at a time, then check every page that uses it.
7. **Roll back if needed.** The old functions keep running until February 1, so restoring the old URL is your safety net.

Where do the hidden callers live? Not only in templates and modules, but also in page's additional code (head and footer HTML), workflows and external apps that call the functions directly (like Zapier, for example). HubSpot's [migration guide](https://developers.hubspot.com/docs/cms/reference/serverless-functions/migrate-design-manager-serverless-to-projects) has a good checklist of these places.

A few technical differences worth knowing before you start:

|  | Design Manager (old) | Developer projects (new) |
| --- | --- | --- |
| URL | `/_hcms/api/<path>` | `/hs/serverless/<path>` |
| Runtime | Node.js 18 or 20 | Node.js 24 (set by platform version) |
| Packages | Preloaded `axios` 0.19, `request`, `@hubspot/api-client` | Nothing preloaded, any npm package via `package.json` |
| Environment variables | `environment` in `serverless.json` | Not supported, use secrets |
| Rate limit info | `context.limits` | Not available, only a `429` response |
| Deploy | Live immediately | Numbered builds, rollback to any build |

## What actually gets better

It's not all pain. A few things are genuinely better on the developer platform.

- **15 seconds instead of 10.** A function can now run for 15 seconds before it times out. For functions that call slow external APIs (an ERP, a legacy CRM), those extra 5 seconds can be the difference between "works" and "randomly fails".
- **A modern, maintained runtime.** Node.js 24 with automatic security updates. No more being stuck on a runtime HubSpot can't upgrade, which is exactly why we're all here.
- **You choose your own libraries.** In Design Manager, HubSpot gave every function a fixed set of preinstalled packages, including `axios` version 0.19 from 2020, and you couldn't update them. If you needed anything else, you had to bundle it yourself with webpack. In a project, you list the packages you need in `package.json`, at whatever version you want, and they're installed during the build.
- **Builds and rollbacks.** Every upload is a numbered build, and you can redeploy any previous one with a single command. Design Manager does have version history, so you can restore an older version of a file. But when you're developing a module or a theme, you save every five minutes, and finding the right version among dozens of saves is a challenge of its own.
- **One caveat on limits.** Design Manager functions had a clearly documented account limit: 600 execution seconds per minute in total, plus `context.limits` to tell you how close you were. The new reference mentions the 15-second timeout and possible cold starts, but a per-minute account limit isn't mentioned anywhere. That doesn't necessarily mean there's no limit, only that it isn't documented. And `context.limits` is gone: the only signal is a `429` response (error: “too many requests”). So if you're planning to use the longer timeout for heavier functions, don't assume the old 600-second budget still applies. Handle `429` in your front-end code and load-test anything that gets real traffic.

## What hurts

Now the less pleasant part.

- **HubSpot is moving serious development to the CLI, whether you wanted it or not.** As I mentioned above, server-side code now lives in developer projects. Design Manager was never perfect, but it was accessible: anyone with the right permissions could open a file and fix a bug in the browser. Now you need a local setup, a terminal, Node.js on your machine, an authenticated CLI and a deploy process. For a developer this is normal, but the huge number of developers who work with HubSpot CMS are rather a mix between a developer, a CRM configurator, a marketer, and a content creator, than a developer in the traditional sense. Previously, a basic understanding of HTML, CSS, and a bit of more advanced JavaScript, along with knowledge of HubL (even at a beginner level), was enough to create custom modules, themes and simple serverless functions. Not anymore.
- **Old functions can break in unexpected ways.** Here's what happened to us. I added one variable to an existing endpoint in Design Manager (just before editing was prohibited) and saved it. The function crashed. Not because of my change: the logs showed that `axios` had simply stopped loading inside the function. Nobody had touched the packages, nobody had updated anything, only the JavaScript file changed. Something on HubSpot's side was different when the function was re-saved, and I still don't know exactly what. Since November 17 you can't edit Design Manager functions at all, so you won't hit this exact problem anymore. But the lesson stands: these functions run on infrastructure HubSpot is winding down, and "it still runs until February 1" doesn't mean "nothing will surprise you until February 1". And if something does break now, you can't fix it in Design Manager. The only fix is migrating. So it's better not to put this off for too long.
- **Very short notice.** The sunset was announced and went live on the same day, November 3, and editing was blocked just two weeks later, on November 17. Partners on the HubSpot Community were vocal about it: many found out from their clients, not from HubSpot. From the announcement to the shutdown, the whole window is about three months, right across the holiday season. That's tight for agencies managing dozens of portals, and it's why I'd recommend starting now rather than in January.

## Can AI do it for you?

HubSpot's migration guide calls an AI coding agent the recommended path. It ships a ready-made prompt for Claude Code, Cursor or VS Code with GitHub Copilot, and the agent asks for your approval before every upload, deploy or change on the live site. It's a well-written prompt.

Now the honest part. I migrated three endpoints by hand, and it took about 15 minutes. A junior developer with a half-working brain (the other half is thinking about where to find a freelance project — that's life) and a basic idea of what a terminal is (yes, that black window with the letters) would do it in the same 15 minutes. Fine, maybe 20. Most of my time didn't go into the migration at all. It went into checking logs and explaining to the client what happened and why any of this was necessary.

So is AI worth it here? It depends on what you're migrating.

**What the agent needs from you.** The HubSpot CLI (8.4.0 or later), Node.js on your machine, the HubSpot developer MCP server installed in your coding tool, and an authenticated account. That's a developer setup. If you don't know what a terminal is, you'll get stuck before the agent writes a single line. And even after that, you need to judge every approval it asks for, on your live website. The agent also never creates secrets itself: it gives you the `hs secret` commands to run.

**What about credits?** You will spend tokens, just not HubSpot’s. The agent runs in your own coding tool (Claude Code, Cursor and so on), so it uses that tool’s subscription or API budget. The developer MCP server itself runs locally on your machine, installed through the CLI, and I couldn’t find it among the features that consume HubSpot credits. Which also means the AI route isn’t an alternative to the CLI: it’s the CLI plus an AI tool on top. By the time you’ve installed the CLI, authenticated it and set up the MCP server, you’ve already done most of the work the migration itself needs. So for a simple migration, the “recommended” AI route is essentially the same manual work, with an extra layer and an extra bill. Why it’s the recommended path for everyone, I honestly don’t know.

And let’s be realistic about who has serverless functions in the first place. Companies on Content Hub Enterprise with custom server-side logic usually aren’t getting one or two leads a day. They’re getting dozens, sometimes hundreds. For them, the real work isn’t moving the endpoint, it’s everything around it: watching logs, testing every form and integration, and reporting to the client (or your boss) that everything works, or explaining why it doesn’t. Next to that, the 15 to 20 minutes it takes to actually migrate an endpoint is the minor part of the job.

**Where it actually helps.** Not in rewriting the function. That part is small: HubSpot generates the project, you move the code, register the endpoint, deploy. The hard part is finding every place that calls the function. On older portals that went through several agencies, a call can hide in a blog footer or a single page's head HTML. An agent that methodically searches everything and keeps an inventory saves real time here.

So here's how I'd decide:

| Your situation | What I'd do |
| --- | --- |
| One or two simple functions, you're comfortable with a terminal | Migrate by hand. Setting up the agent takes longer than the migration |
| Many functions, an older portal, nobody knows where everything is called | Use the agent, mostly for discovery and the inventory |
| No development experience | Neither. You’re better off not doing it yourself: ask your developer or a HubSpot Solutions Partner. |

## Also affected: workflow custom code actions and older projects

The same announcement covers two more things that are easy to miss.

**Custom code actions in workflows.** Node.js 20 and earlier are being retired here too. Since November 3 you can't create new Node.js 20 actions, and since November 17 you can't save changes to existing ones. They keep running, but the upgrade to Node.js 24 isn't just a dropdown: Node.js 24 doesn't support callback-style handlers, and library versions changed, so each action needs updating and testing. HubSpot says Breeze can update the custom code actions in a workflow for you. Unlike serverless functions, this doesn't require Content Hub Enterprise, so check your workflows even if the rest of this article doesn't apply to you.

The same Node.js vulnerability applies here, and HubSpot sent a separate security email about it. Its advice is more cautious than for serverless functions: turn off workflows with Node.js custom code actions until you've updated them, rotate the secrets and tokens those actions use, then switch the runtime to Node.js 24, update and test the code, and turn the workflows back on.

**Projects on older platform versions.** If you already moved functions to developer projects earlier, check the platform version. Projects on `2023.1`, `2023.2` or `2025.1` also run Node.js 18 or 20, and builds on those versions are already blocked. Upgrade with `hs project migrate` and redeploy. Projects on `2025.2`, `2026.03` or `2026.09` are fine.

## Your checklist before February 1, 2027

- Check whether your account has Content Hub Enterprise
- List all Design Manager serverless functions and their endpoints
- Find every caller: templates, modules, JavaScript, site and blog header/footer HTML, page head HTML, rich text, external apps
- Retire functions nobody uses instead of migrating them
- Rotate the secrets and tokens your functions use
- Migrate the rest to a developer project on the current platform version
- Switch callers one function at a time and test every page
- Handle `429` responses in your front-end code
- Check workflow custom code actions on Node.js 20 or earlier
- Check existing developer projects on old platform versions
- Finish in January, not on January 31

## FAQ

If you scrolled straight down here, we get it. Here’s the short version. 

### What happens if I don’t migrate by February 1, 2027?

Your Design Manager serverless functions stop running, and every request to `/_hcms/api/` fails. Any feature on your site that depends on them (forms, calculators, integrations) will break.

### Do I need Content Hub Enterprise to be affected?

Yes. Serverless functions require Content Hub Enterprise, so if you don’t have it, your site has no serverless functions to migrate. Workflow custom code actions are a separate case, so check those anyway.

### Can HubSpot migrate my functions for me?

No. Every function and every page that calls it is unique, so HubSpot can’t do it automatically. It provides a migration guide and an AI prompt, but someone still has to run the migration and test it.

### Do I need to change my templates and modules?

In most cases, only one thing: the URL they call. `/_hcms/api/your-endpoint` becomes `/hs/serverless/your-endpoint`. The templates and modules themselves can stay in Design Manager.

### How long does the migration take?

For a few simple functions, not long: I migrated three endpoints in about 15 minutes. What takes time is finding every place a function is called, testing, and (in our case) explaining to the client why it was necessary. Older portals with many functions take longer.

### Are workflow custom code actions affected too?

Yes. Custom code actions on Node.js 20 or earlier can no longer be created or edited, and HubSpot recommends moving them to Node.js 24. The upgrade needs code changes, so plan time to update and test them.

## Sources

- [Sunsetting design manager serverless functions and older Node.js runtimes for custom code actions](https://developers.hubspot.com/changelog/sunsetting-design-manager-serverless-functions-and-older-node.js-runtimes-for-custom-code-actions), HubSpot Developer Changelog
- [Migrate design manager serverless functions to developer projects](https://developers.hubspot.com/docs/cms/reference/serverless-functions/migrate-design-manager-serverless-to-projects), HubSpot developer docs
- [Serverless functions reference (design manager)](https://developers.hubspot.com/docs/cms/reference/serverless-functions/serverless-functions), for the old limits
- [Serverless functions reference (developer platform)](https://developers.hubspot.com/docs/apps/developer-platform/add-features/serverless-functions/reference), for the new limits
- [HubSpot Community thread on the sunset](https://community.hubspot.com/t/sunsetting-design-manager-serverless-functions-and-older-node-js-runtimes-for-custom-code-actions/163902)
- [Set up the developer MCP server](https://developers.hubspot.com/docs/developer-tooling/local-development/developer-mcp/setup)
- [Developer platform and API versioning](https://developers.hubspot.com/docs/developer-tooling/platform/versioning)

## Need any help?

Not sure whether your site uses serverless functions, or don’t have time to migrate them before the deadline? Contact us. We’ll find every place your functions are called and move them to developer projects with a tested rollback path.

[![Max Vorozhtsov](https://www.growpoland.pl/hubfs/max-vorozhtsov.jpg)](https://www.growpoland.pl/en/blog/author/max-vorozhtsov)

[Max Vorozhtsov](https://www.growpoland.pl/en/blog/author/max-vorozhtsov)

 Front-end Lead in Grow

In web-development since 2010. HubSpot and Oracle certified Front-end Developer, also has an experience as a manager, tester and content creator. 

[![Max Vorozhtsov LinkedIn](https://www.growpoland.pl/hs-fs/hubfs/Grow%20Site/linkedin-color.png?width=25&height=25&name=linkedin-color.png)](https://www.linkedin.com/in/max-vorozhtsov/)

Read more

## Similar articles

<https://www.growpoland.pl/en/blog/cms-hub-or-content-hub>

HubSpot, HubSpot CMS, AI

### [Two Years Later, People Still Confuse CMS Hub and Content Hub. Let's Fix That.](https://www.growpoland.pl/en/blog/cms-hub-or-content-hub)

Max Vorozhtsov

You'll read it in 15 min

<https://www.growpoland.pl/en/blog/hubspot-vs-wordpress-or-why-you-should-switch-to-hubspot-in-2024>

HubSpot, WebDevelopment, HubSpot CMS

### [HubSpot vs WordPress or why you should switch to HubSpot in 2024](https://www.growpoland.pl/en/blog/hubspot-vs-wordpress-or-why-you-should-switch-to-hubspot-in-2024)

Max Vorozhtsov

You'll read it in 7 min

<https://www.growpoland.pl/en/blog/a-b-testing-in-the-hubspot-cms>

HubSpot CMS

### [A/B Testing in the HubSpot: Boost Your Conversions](https://www.growpoland.pl/en/blog/a-b-testing-in-the-hubspot-cms)

Max Vorozhtsov

You'll read it in 8 min

<https://www.growpoland.pl/en/blog/hubspot-cms-pricing-explained>

HubSpot

### [Is HubSpot really expensive? HubSpot CMS pricing explained](https://www.growpoland.pl/en/blog/hubspot-cms-pricing-explained)

Max Vorozhtsov

You'll read it in 10 min

<https://www.growpoland.pl/en/blog/optimize-your-website-with-hubspot-website-grader-free-tool>

HubSpot, WebDevelopment, HubSpot CMS

### [Optimize Your Website with HubSpot Website Grader \[free tool\]](https://www.growpoland.pl/en/blog/optimize-your-website-with-hubspot-website-grader-free-tool)

Max Vorozhtsov

You'll read it in 8 min

<https://www.growpoland.pl/en/blog/is-aeo-the-new-seo>

HubSpot CMS, AI

### [Is AEO the new SEO? Plus 15 more questions we answer every day](https://www.growpoland.pl/en/blog/is-aeo-the-new-seo)

Max Vorozhtsov

You'll read it in 24 min

<https://www.growpoland.pl/en/blog/how-to-implement-ai-with-node-js>

WebDevelopment, AI

### [How to implement AI with Node.js? The advantage of JavaScript over Python in the world of LLM](https://www.growpoland.pl/en/blog/how-to-implement-ai-with-node-js)

Max Vorozhtsov

You'll read it in 15 min

<https://www.growpoland.pl/en/blog/is-jquery-really-dead-in-2023>

WebDevelopment

### [Is jQuery really dead in 2023?](https://www.growpoland.pl/en/blog/is-jquery-really-dead-in-2023)

Max Vorozhtsov

You'll read it in 7 min

<https://www.growpoland.pl/en/blog/how-to-create-a-chatbot-with-hubspot>

Customer Success, HubSpot, HubSpot CMS, AI

### [How to create a chatbot with HubSpot?](https://www.growpoland.pl/en/blog/how-to-create-a-chatbot-with-hubspot)

Max Vorozhtsov

You'll read it in 8 min

<https://www.growpoland.pl/en/blog/migrating-to-hubspot-cms-5-tips-for-a-smooth-transition>

HubSpot

### [Migrating to HubSpot CMS: 5 Tips for a Smooth Transition](https://www.growpoland.pl/en/blog/migrating-to-hubspot-cms-5-tips-for-a-smooth-transition)

Max Vorozhtsov

You'll read it in 5 min

## Chcesz wdrożyć HubSpot albo masz jakieś inne pytania?

[![Icon\_calendar](https://www.growpoland.pl/hubfs/Icon_calendar.svg) Schedule a meeting with CEO](https://meetings.hubspot.com/adam-malachowski) [![CONTACT\_phone icon](https://www.growpoland.pl/hubfs/CONTACT_phone%20icon.svg) +48 668 258 500](tel:48%20668%20258%20500) [![Group 1082](https://www.growpoland.pl/hubfs/Group%201082.svg) info@growpoland.pl](mailto:info@growpoland.pl)

![Adam Małachowski (CEO Grow Poland)](https://www.growpoland.pl/hubfs/adam-malachowski.png)

![FORM SHADOW-1](https://www.growpoland.pl/hubfs/FORM%20SHADOW-1.png)

![grow-logo-white-transparent](https://www.growpoland.pl/hubfs/grow-logo-white-transparent.png)

Grow Poland Sp. z o.o.

Konstruktorska 11 (Adgar BIT), 5th floor

02-673 Warsaw, Poland

+48 668 258 500

[![Grow Poland in LinkedIn](https://www.growpoland.pl/hubfs/LINKEDIN%20ICON.svg)](https://pl.linkedin.com/company/grow-poland) [![Grow Poland in Facebook](https://www.growpoland.pl/hubfs/FB%20ICON.svg)](https://pl-pl.facebook.com/growpoland/) [![Grow Poland in X](https://www.growpoland.pl/hubfs/x-white-icon.webp)](https://x.com/growpoland)

[Privacy Policy](https://www.growpoland.pl/en/privacy-policy)

All rights reserved. Grow Poland 2026

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Max Vorozhtsov",
    "url" : "https://www.growpoland.pl/en/blog/author/max-vorozhtsov"
  },
  "datePublished" : "2026-11-19T11:04:07",
  "description" : "HubSpot is shutting down serverless functions built in Design Manager: what is changing, how to check whom it affects &amp; what the migration looks like in practice.",
  "headline" : "Design Manager Serverless Functions Are Going Away. What Now?",
  "image" : "https://5265844.fs1.hubspotusercontent-eu1.net/hubfs/5265844/hubspot-serverless.jpg",
  "mainEntityOfPage" : {
    "@id" : "https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "ProfessionalService",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.growinternational.eu/hubfs/grow-smarketing-nb.png"
    },
    "name" : "Grow Poland"
  }
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Max Vorozhtsov",
    "url" : "https://www.growpoland.pl/en/blog/author/max-vorozhtsov"
  },
  "dateModified" : "2026-11-19T11:45:21.335Z",
  "datePublished" : "2026-11-19T11:04:07.000Z",
  "headline" : "Design Manager Serverless Functions Are Going Away. What Now?",
  "image" : [ "https://www.growpoland.pl/hubfs/hubspot-serverless.jpg" ],
  "mainEntityOfPage" : {
    "@id" : "https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.growpoland.pl/hubfs/Grow%20treansparent.png"
    },
    "name" : "Grow Poland sp. z o.o."
  }
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://www.growpoland.pl/#organization",
  "@type" : "ProfessionalService",
  "address" : {
    "@type" : "PostalAddress",
    "addressCountry" : "PL",
    "addressLocality" : "Warszawa",
    "postalCode" : "02-673",
    "streetAddress" : "Konstruktorska 11"
  },
  "logo" : "https://www.growpoland.pl/hubfs/grow-smarketing-nb.png",
  "name" : "Grow Poland",
  "openingHoursSpecification" : {
    "@type" : "OpeningHoursSpecification",
    "closes" : "18:00",
    "dayOfWeek" : [ "Monday", "Tuesday", "Wednesday", "Thursday", "Friday" ],
    "opens" : "09:00"
  },
  "sameAs" : [ "https://www.facebook.com/growpoland/", "https://x.com/GrowPoland", "https://www.linkedin.com/company/grow-poland/" ],
  "telephone" : "+48 668 258 500",
  "url" : "https://www.growpoland.pl/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away#faq",
  "@type" : "FAQPage",
  "inLanguage" : "en",
  "isPartOf" : {
    "@id" : "https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away",
    "@type" : "WebPage"
  },
  "mainEntity" : [ {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Your Design Manager serverless functions stop running, and every request to /_hcms/api/ fails. Any feature on your site that depends on them (forms, calculators, integrations) will break."
    },
    "name" : "What happens if I don't migrate by February 1, 2027?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Yes. Serverless functions require Content Hub Enterprise, so if you don't have it, your site has no serverless functions to migrate. Workflow custom code actions are a separate case, so check those anyway."
    },
    "name" : "Do I need Content Hub Enterprise to be affected?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "No. Every function and every page that calls it is unique, so HubSpot can't do it automatically. It provides a migration guide and an AI prompt, but someone still has to run the migration and test it."
    },
    "name" : "Can HubSpot migrate my functions for me?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "In most cases, only one thing: the URL they call. /_hcms/api/your-endpoint becomes /hs/serverless/your-endpoint. The templates and modules themselves can stay in Design Manager."
    },
    "name" : "Do I need to change my templates and modules?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "For a few simple functions, not long: I migrated three endpoints in about 15 minutes. What takes time is finding every place a function is called, testing, and (in our case) explaining to the client why it was necessary. Older portals with many functions take longer."
    },
    "name" : "How long does the migration take?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Yes. Custom code actions on Node.js 20 or earlier can no longer be created or edited, and HubSpot recommends moving them to Node.js 24. The upgrade needs code changes, so plan time to update and test them."
    },
    "name" : "Are workflow custom code actions affected too?"
  } ],
  "url" : "https://www.growpoland.pl/en/blog/design-manager-serverless-functions-are-going-away"
}
```