HACS is gone: migrating to the Marketplace

Home Assistant 2026.11 — described by the team as their biggest release ever — absorbed HACS into a built-in Marketplace at Settings → Marketplace. If you already had HACS, your integrations and cards mostly migrated on their own. Mostly. This guide is the part the release notes skip: the failure modes that leave things installed but quietly frozen, and the checklist that proves your migration actually worked.

Published Nov 18, 2026

What actually changed

The Marketplace is HACS's catalog, moved into core: the same community integrations, themes and dashboard cards, now browsable and installable from Settings → Marketplace without a GitHub account for the catalog itself. The standalone HACS installer is blocked on 2026.11 and later — there is no 'keep the old HACS' path on a current system, which is why this is a migration and not a preference. Your installed items were carried over automatically during the upgrade; the machinery that checks them for updates is what changed underneath.

Back up first→Update to 2026.11→Open the Marketplace→Audit your repos→Verify updates flow

The three ways the migration quietly fails

The only rollback is a backup. There is no downgrade button and no supported 'undo' for the Marketplace move. Take a full backup before upgrading to 2026.11 — our backups guide covers the routine — and keep it until the checklist below passes.

The post-upgrade checklist

  1. Open Settings → Marketplace → Installed and count. Compare against what you had: every integration, card and theme you rely on should be listed. Anything missing gets reinstalled from the catalog — your configuration for it survives, because config lives with the integration, not the installer.
  2. Hunt the frozen ones: any item that came from a custom repository deserves a manual check. If its repo lacks hacs.json, the Marketplace cannot offer updates — your options are to watch the repo yourself, switch to a maintained alternative, or accept the freeze knowingly.
  3. Check AppDaemon and Python scripts separately and decide their fate deliberately — they are the two categories the migration does not babysit.
  4. Open every dashboard you care about. Red 'custom element' boxes mean a card's resource registration was lost; reinstalling that card from the Marketplace re-registers it.
  5. If you have templates or automations referencing HACS entities (update sensors were the common one), re-point them at the Marketplace equivalents — names changed under some of them.
  6. Live with it for 48 hours, then confirm at least one installed item has either updated or reported 'up to date' through the new path. That is the proof the pipe works, not just the catalog.

Should you upgrade today?

If you run HACS content you depend on, the honest answer is: yes, but on a calm evening with a backup in hand — not because 2026.11 is dangerous, but because you are the test suite for your particular pile of community code. The release also renames entities in a backward-incompatible way (our companion guide covers the entity-naming rework), so budget an hour for the pair of changes together rather than discovering them separately. Readers on TrueNAS's deprecated app have a different first step — migrate the install itself first, per our TrueNAS migration guide.

Troubleshooting

Official documentation and references

Frequently asked questions

Do I need a GitHub account for the Marketplace?

Not for browsing and installing the standard catalog — removing that requirement was one of the headline changes. A GitHub account still matters for some custom-repository workflows, but the old HACS onboarding wall is gone.

Will my existing HACS integrations keep working after 2026.11?

Yes — they migrate with the upgrade and keep running. The risk is not breakage, it is silence: a minority of items (custom repos without hacs.json, AppDaemon apps, Python scripts) can lose their update path. The checklist in this guide finds them.

Can I stay on the old HACS instead?

Not on 2026.11 or later — the installer is blocked and the old update path is retired. Staying on 2026.10 forever is technically possible and strategically poor; migrate deliberately instead.

Related guides