FREE · NO EMAIL REQUIRED
Five checks before migrating a CRM card.
Send this to the person who maintains your HubSpot app. Use it to organize the next conversation—not as a diagnosis of your integration.
HubSpot’s published legacy-card sunset is October 31, 2026. The deadline alone does not establish that your app is affected. Official migration guide · checked September 8, 2026.
Confirm the card type.
Identify whether the app still contains legacy CRM cards. Modern React cards and an API connection alone do not establish exposure to this sunset.
Identify the source owner.
Record who maintains the app and backend, the card definitions, and supported record types. Prepare sanitized examples for a source review.
Inventory what users do.
List fields, actions, links, loading and error states. Note ticket/helpdesk surfaces, permissions and unanswered questions before pricing changes.
Plan replacement tests.
Use a test environment to check behavior and access. Making an app card available is different from replacing the legacy card in existing views.
Approve the view migration.
Review test evidence with an authorized administrator first. HubSpot says its card-view migration cannot be stopped or reversed.
Steps 1, 4 and 5 summarize HubSpot guidance linked above. Source ownership and the inventory are our preparation recommendations. This educational checklist does not inspect your app or guarantee compatibility. AI-assisted, independently offered; no HubSpot affiliation.
Need an app-specific change and test plan?
$750 USD + applicable tax buys an independent source review of up to two legacy cards in one public or unlisted app. Delivery within two business days after start and acceptance of complete sanitized inputs. Implementation is separate, from $4,500.