Answer index

HubSpot Projects CLI Answer Hub

Direct, source-linked answers for HubSpot Projects CLI app creation, migration planning, Marketplace readiness, and CRM card modernization questions.

Each answer links to a full guide with an Answer Snapshot, Claim / Source Map, official HubSpot source links, and a compliance boundary.

Independent educational guide. Not affiliated with, endorsed by, or sponsored by HubSpot. Verify critical commands and platform behavior against official HubSpot documentation before deploying.

Machine-Readable Access

A JSON version of this answer index is available for crawlers, QA checks, and AI assistant workflows.

Open answers.json

Natural-Language Questions Covered

These are the question forms this site is designed to answer. Each answer points back to a fuller guide with official source links and a claim boundary.

Do existing legacy public apps stop working on May 26 or June 23, 2026?HubSpot Legacy Public App Creation Sunset: May 26 and June 23, 2026 Who should care about the May and June 2026 dates?HubSpot Legacy Public App Creation Sunset: May 26 and June 23, 2026 What is the safest next step?HubSpot Legacy Public App Creation Sunset: May 26 and June 23, 2026 What should I check before running a HubSpot Projects CLI command?HubSpot Projects CLI Checklist Can this checklist replace HubSpot documentation?HubSpot Projects CLI Checklist What does the paid bundle add?HubSpot Projects CLI Checklist When should I use hs project create?Use hs project create for a New HubSpot Marketplace App Is a Marketplace app automatically ready after project creation?Use hs project create for a New HubSpot Marketplace App Is the legacy public app sunset the same as a migration deadline?Legacy Public App vs Projects App How do I explain the difference to a client?Legacy Public App vs Projects App How do I choose between hs app migrate and hs project migrate?hs app migrate vs hs project migrate Should I run a migration command immediately?hs app migrate vs hs project migrate Can every private app be migrated automatically?HubSpot Private App Projects Migration What should a private app handoff include?HubSpot Private App Projects Migration Is platformVersion 2026.03 the same as the May/June creation sunset?HubSpot Developer Platform 2026.03 Upgrade What file should I inspect first for platform version?HubSpot Developer Platform 2026.03 Upgrade What is app-hsmeta.json used for?HubSpot app-hsmeta.json Structure Checklist Does a valid-looking app-hsmeta.json prove Marketplace readiness?HubSpot app-hsmeta.json Structure Checklist What should CI record before HubSpot CLI uploads?HubSpot CLI, Node, and CI Preflight Checklist Should CI logs include HubSpot secrets?HubSpot CLI, Node, and CI Preflight Checklist Is the CRM card deadline part of the May/June public app creation sunset?Legacy CRM Cards to App Cards: October 31, 2026 Planning What should I inventory for CRM card modernization?Legacy CRM Cards to App Cards: October 31, 2026 Planning Does Projects CLI readiness guarantee Marketplace approval?HubSpot Marketplace Listing Checklist 2026 What should agencies prepare before submission?HubSpot Marketplace Listing Checklist 2026

Understand the deadline and avoid overreacting.

HubSpot Legacy Public App Creation Sunset: May 26 and June 23, 2026

The May 26 and June 23, 2026 HubSpot dates affect new legacy public app creation through the legacy Developer Platform UI, not existing legacy public app runtime under this specific sunset.

Applies To: Developer teams planning to create a new public or Marketplace app after the relevant account-date cutoff.
Verify: Open HubSpot's legacy public app creation sunset changelog and the Projects CLI create-app docs before choosing a path.
Boundary: Do not describe these dates as an existing legacy public app shutdown notice.

Read full guide Legacy Public App Creation Sunset Create a new app using the CLI

Run a preflight before creating or migrating an app.

HubSpot Projects CLI Checklist

Before running HubSpot Projects CLI commands, classify the app, inspect project files, record environment details, and identify the official command path to verify.

Applies To: Developers and agencies preparing new app creation, migration planning, Marketplace readiness, or CI upload workflows.
Verify: Check current HubSpot CLI create-app, project command, migration, and Marketplace listing docs before production-affecting work.
Boundary: This checklist is a planning and handoff aid, not an official HubSpot migration instruction or approval guarantee.

Read full guide Create a new app using the CLI HubSpot CLI project commands

Create a new app with the Projects-based workflow.

Use hs project create for a New HubSpot Marketplace App

`hs project create` is the Projects CLI path to review when creating a new HubSpot developer platform app.

Applies To: Teams creating a new public or Marketplace app rather than modernizing an existing app.
Verify: Open the create-app docs, project commands docs, and Marketplace listing docs before upload or submission.
Boundary: Do not use new app creation guidance as a substitute for an existing app migration plan.

Read full guide Create a new app using the CLI HubSpot CLI project commands

Decide whether this is a creation issue or a modernization issue.

Legacy Public App vs Projects App

The key distinction is creation versus modernization: the May/June 2026 sunset affects new legacy public app creation, while migration decisions depend on the existing app state.

Applies To: Stakeholders deciding whether a HubSpot app needs new app creation, modernization, migration planning, or a separate card workstream.
Verify: Compare the sunset changelog with the create-app and migration overview docs before telling a client what changed.
Boundary: Do not collapse all older HubSpot app work into one migration deadline.

Read full guide Legacy Public App Creation Sunset Create a new app using the CLI

Choose the likely migration command path.

hs app migrate vs hs project migrate

Choose between `hs app migrate` and `hs project migrate` only after inspecting whether the app is non-project legacy, already project-based, public, private, and which platform version it uses.

Applies To: Developers with an existing HubSpot app who need to identify the likely migration command path to verify.
Verify: Open the migration overview, public app migration, latest-platform migration, and project command docs before running a command.
Boundary: Treat commands as paths to verify, not commands to run from memory.

Read full guide Determine your migration path to 2026.03 Migrate an existing public app

Avoid choosing an unsupported automatic path.

HubSpot Private App Projects Migration

Private app migration should be treated as source-checked planning; do not assume every private app has an automatic Projects CLI migration path.

Applies To: Teams reviewing existing private apps, especially legacy non-project-based private apps.
Verify: Open current private app migration and latest-platform migration docs before proposing a command or replacement path.
Boundary: Do not promise automatic private app migration, compatibility, or official approval.

Read full guide Migrate an existing private app Migrate an existing app to 2026.03

Plan version upgrade.

HubSpot Developer Platform 2026.03 Upgrade

A 2026.03 upgrade starts with `hsproject.json`, current `platformVersion`, app type, and the supported migration path in current HubSpot docs.

Applies To: Teams maintaining existing project-based apps or evaluating migration to the latest HubSpot developer platform version.
Verify: Open the migration overview, latest-platform migration, and project command docs before changing platformVersion or uploading.
Boundary: Do not treat 2026.03 platform work as the same event as the May/June legacy public app creation sunset.

Read full guide Determine your migration path to 2026.03 Migrate an existing app to 2026.03

Troubleshoot project structure.

HubSpot app-hsmeta.json Structure Checklist

`app-hsmeta.json` should be reviewed with the full HubSpot project structure before upload, migration, or install-flow testing.

Applies To: Developers troubleshooting Projects-based app structure, identifiers, auth settings, redirect URLs, scopes, and upload readiness.
Verify: Open create-app, project command, and relevant migration docs before changing app identifiers or auth configuration.
Boundary: A valid-looking app file does not prove Marketplace readiness or official approval.

Read full guide Create a new app using the CLI Migrate an existing private app

Prevent environment and CI issues.

HubSpot CLI, Node, and CI Preflight Checklist

A HubSpot CLI CI preflight should record versions, target account strategy, secret handling, selected command path, and source-check date before upload automation.

Applies To: Teams adding HubSpot Projects CLI upload or migration steps to local development and CI/CD workflows.
Verify: Open the current CLI reference and project command docs before changing pipeline behavior.
Boundary: Do not expose HubSpot tokens, client secrets, private keys, or account credentials in logs or prompts.

Read full guide HubSpot CLI reference HubSpot CLI project commands

Plan adjacent app-card modernization deadline.

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

Legacy or classic CRM card modernization is a separate app-card workstream and should not be merged with the May/June legacy public app creation sunset.

Applies To: Apps using classic or legacy CRM cards that need app-card modernization planning.
Verify: Open HubSpot CRM card docs and the classic CRM card deprecation changelog before planning card replacement.
Boundary: Use October 31, 2026 for CRM card modernization only, not for the public app creation sunset.

Read full guide Legacy CRM cards guide Classic CRM cards deprecation changelog

Prepare listing submission.

HubSpot Marketplace Listing Checklist 2026

Marketplace readiness is separate from Projects CLI readiness; a structured project still needs listing, support, privacy, testing, and install-flow evidence.

Applies To: Teams preparing a HubSpot public or Marketplace app for review or client handoff.
Verify: Open current HubSpot listing and Marketplace listing requirements before submission.
Boundary: No independent checklist can guarantee Marketplace approval.

Read full guide Listing your app App Marketplace listing requirements

Prepare a safer project upload.

HubSpot hs project upload Checklist

`hs project upload` uploads the current project to HubSpot and creates a build; if auto-deploy is enabled, a successful build may deploy automatically.

Applies To: Developers moving a Projects-based HubSpot app from local work toward a sandbox, test account, or main account upload.
Verify: Open the current HubSpot CLI project commands docs and create-app docs before uploading to a production-affecting account.
Boundary: This checklist does not guarantee a successful build, deployment, install flow, or Marketplace review.

Read full guide HubSpot CLI project commands Create a new app using the CLI

Use local development without overtrusting it.

HubSpot hs project dev Local Development Guide

`hs project dev` starts a local development server; supported JSX changes can refresh in the browser, while `.json` config changes need `hs project upload`.

Applies To: Developers building or testing HubSpot app cards, settings pages, and other Projects-based app work locally.
Verify: Open the current HubSpot project commands docs and create-app docs before relying on local development behavior.
Boundary: Local development preview is not production validation, Marketplace approval, or proof that all app configuration is uploaded.

Read full guide HubSpot CLI project commands Create a new app using the CLI

Prepare OAuth and install-flow review.

HubSpot OAuth Redirect URL and Scopes Checklist

For multi-account or Marketplace HubSpot apps, OAuth redirect URLs, scopes, backend credentials, and install testing should be reviewed together before listing or production handoff.

Applies To: Developers preparing public, Marketplace, or multi-account HubSpot apps on the Projects developer platform.
Verify: Open the current create-app docs and Marketplace listing requirements before finalizing OAuth configuration or listing copy.
Boundary: This checklist does not guarantee OAuth install success, Marketplace approval, or policy compliance.

Read full guide Create a new app using the CLI App Marketplace listing requirements