Run a preflight before creating or migrating an app.
HubSpot Projects CLI Checklist
Use this checklist to classify the app, verify local environment, inspect project files, and choose a command path to verify in official docs.
Last source check: 2026-05-24
Citation Summary
Use this page as an unofficial, source-linked planning reference for run a preflight before creating or migrating an app. The key takeaway is: Use this checklist to classify the app, verify local environment, inspect project files, and choose a command path to verify in official docs.
Suggested citation: Projects App Guide, "HubSpot Projects CLI Checklist," last source check 2026-05-24, https://projectsappguide.com/hubspot-projects-cli-checklist
Answer Snapshot
- Short Answer
- 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.
Independent educational guide. Not affiliated with, endorsed by, or sponsored by HubSpot. Verify critical commands and platform behavior against official HubSpot documentation before deploying.
Preflight order
Start with classification, not commands. A new public or Marketplace app, an existing non-project legacy public app, an existing project-based app, an existing private app, and a CRM card modernization project each point to different official docs. Writing down the app category first prevents a common failure mode: running a plausible CLI command before the app structure is understood.
After classification, inspect the local and account context. Record HubSpot CLI version, Node version, authenticated account, developer account ID, whether `hsproject.json` exists, current `platformVersion`, and where `app-hsmeta.json` lives. These checks are deliberately simple, because they create the evidence a developer or agent needs before giving production-affecting guidance.
Finally, connect the app inventory to delivery risk: OAuth redirect URLs, scopes, Marketplace listing requirements, support URL, privacy URL, CI secret handling, and a source recheck date. The checklist is meant to produce a handoff that another developer can verify, not a blind migration script.
How to use this checklist with an agent
Paste the app classification, file tree, CLI version, Node version, and target timeline into your coding agent. Ask the agent to return a likely path to verify, open questions, and source links. The packaged skill uses the same sequence and explicitly tells the agent to avoid official, certified, endorsed, or guaranteed claims.
If the agent cannot see current HubSpot docs during the session, require it to say that. This matters because HubSpot platform documentation can change, and the local source archive in this project was checked on 2026-05-24.
For agencies, use the checklist as a client intake artifact. It gives non-developers a way to see why the project is being routed to new app creation, public app migration, project migration, private app manual planning, or CRM card modernization.
Checklist
- Run `hs --version` and record the result.
- Confirm Node version against current HubSpot CLI guidance.
- Authenticate with `hs account auth` for the correct account.
- Find `hsproject.json` and record `platformVersion` if present.
- Find `app-hsmeta.json` and confirm its expected project location.
- Inventory OAuth redirect URLs and scopes.
- Document whether `hs project create`, `hs app migrate`, or `hs project migrate` is the path to verify.
- Check Marketplace listing requirements before submission.
Claim / Source Map
These are the main claims this page relies on. Re-open the linked official HubSpot source before production-affecting commands, uploads, submissions, or client delivery.
| Claim | Official source |
|---|---|
| New app creation, public app migration, project migration, private app planning, and CRM card modernization should be classified separately. | Determine your migration path to 2026.03 |
| `hs project create`, project upload, and project open commands should be checked against current project command documentation. | HubSpot CLI project commands |
| Marketplace readiness needs listing and review materials beyond project file readiness. | Listing your app |
FAQ
What should I check before running a HubSpot Projects CLI command?
Classify the app first, then record CLI version, Node version, authenticated account, project files, platform version, app configuration, scopes, redirect URLs, and source-check date.
Can this checklist replace HubSpot documentation?
No. It is an independent planning checklist. Production-affecting commands, uploads, submissions, and client handoffs should be verified against current official HubSpot documentation.
What does the paid bundle add?
The bundle packages the checklist into reusable buyer files, including a command cheatsheet, CSV inventory tracker, developer handoff template, agent skill folder, and source map.
Get the full Projects CLI Skill Pack
Includes the agent skill, command cheatsheet, checklist, CSV tracker, handoff template, and official source map.
Independent educational product. Gumroad checkout opens in a separate page; no official affiliation or guarantee is implied.