HubSpot is retiring classic, also called legacy, CRM cards. If an installed app or custom integration uses one, identify its owner and confirm the replacement. The position of a card in the sidebar alone does not tell you which technology it uses.
I would keep this work focused: preserve the information and actions people need, test the replacement, then remove the old card when migration is complete.
Check the dates against the current migration guide
HubSpot's official pages currently differ. As checked on 21 October 2026:
| Source | What it says |
|---|---|
| Changelog | The sunset is 31 October 2026. New Marketplace apps containing classic cards have not been accepted since 16 June 2025. |
| Migration guide | Legacy cards are removed from customer views on 2 November 2026. The migration UI and API remain available until 1 December 2026, then are discontinued. |
My planning recommendation is to finish before 31 October. The tooling window is not a promise that cards remain visible through November. Confirm the current guidance with the app owner before scheduling production changes.
Identify which cards are affected
This sunset concerns cards built with the legacy CRM extensions technology. It does not mean that every HubSpot record card or every installed app is being retired. React-based app cards are the replacement.
List the apps and custom integrations that add information to CRM records. For each candidate, record:
- The card, record types and locations where people use it.
- The vendor or internal developer responsible for it.
- Whether it uses legacy technology, and the replacement or removal plan.
Ask the owner to confirm the implementation and migration status. Avoid assuming that a large vendor has already migrated, or that an undocumented custom card is safe because it still loads. Ask about the effect on the wider integration too; the card sunset does not guarantee that every other app feature is unaffected.
Choose what to replace, rebuild or remove
For a vendor app, ask for its rollout plan and how to verify the updated card in your account. For custom work, decide whether to reproduce the existing behavior, redesign the card or remove it if it no longer serves a task.
UI extensions use React and can show CRM or external data and support actions. The useful scope depends on data access, permissions and the system behind the card. A migration does not need to become a broader interface project.
My read-only renewal-status card is one example of a focused record interface. The app cards guide explains the wider options.
Build and test the replacement
HubSpot provides a Legacy CRM Card Converter example. Check its documented differences and adapt it to your existing card’s data and actions.
Have the developer follow the current migration guide for the app type and project version. Test in a separate environment before replacing cards in customer views. Include:
- Normal records and missing or unavailable associated data.
- Written status labels, permissions and any actions the card supports.
- Each relevant record type and workspace location.
Ticket cards need particular attention: the migration guide describes separate replacements for the CRM sidebar and help desk sidebar. Confirm both if the legacy card appears in both places.
Replace views only after verification
Building a replacement card and replacing existing user views are separate steps. HubSpot supports view migration through the projects UI or migrate views API. For migrated Marketplace apps, release flags can affect replacement-card visibility and must be handled before the view migration.
View migration cannot be reversed once started. Confirm the replacement and its visibility first, then follow the migration procedure. Verify the completed views, document the new owner and remove the legacy card when it is safe to do so.
The amount of work depends on the card's behavior and dependencies. Estimate it after the inventory and replacement test.
Questions about a particular card? You're welcome to get in touch.