Legacy CRM Cards to App Cards: October 31, 2026 Planning

The CRM card deadline is about card rendering and app-card modernization, not the May/June legacy public app creation sunset. HubSpot's CRM card sources describe an October 31, 2026 deadline for existing apps with classic or legacy CRM cards to migrate those cards.

Treat CRM cards as a second workstream if your app includes them. A team may need both a Projects CLI migration plan and a card modernization plan, but the evidence, deadlines, and acceptance criteria are different.

Do not tell stakeholders that the public app creation sunset itself is the CRM card migration deadline. Keep the two official notices separate in planning docs, client emails, and Gumroad copy.

List every classic or legacy CRM card, the CRM objects it appears on, the data source behind it, and whether the card is static or interactive. Include owners for frontend UI, backend data access, scopes, and QA.

Check whether the app is listed or intended for Marketplace listing, because CRM card status can intersect with listing readiness. Then review current app card and CRM card docs for the replacement path.

If the app also needs a Projects CLI platform migration, sequence the work carefully. Card modernization may touch UI extension code and scopes, while Projects migration may touch project files, app configuration, and platform version.

A good CRM card handoff contains a card inventory, target replacement approach, source links, owner, test plan, and risk notes. It should not be a one-line instruction to run a Projects CLI migration command.

Use October 31, 2026 only for the CRM card migration deadline described in the relevant official sources. Use May 26 and June 23 only for new legacy public app creation.

If current official docs provide newer app-card guidance than this source archive, update the source map and the handoff before client delivery.