hs project migrate to 2026.03 fails with empty componentErrors — migration ID 45071900

Apps Third-Party Apps
1

Running hs project migrate --platform-version 2026.03 (CLI v8.5.0, Node v25.5.0, Windows) on a 2025.1 private app fails at the server-side initial-build stage with no actionable error.

Project details

  • Project: HubSpot-OrgChart
  • App ID: 38555060
  • Portal/Hub ID: 2001761
  • Currently deployed: build #7, platformVersion 2025.01
  • Components: 1 CRM card (Sitecore AE Coverage), 1 app function (getFocusData), 1 PRIVATE_APP, 1 SERVERLESS_PACKAGE

Migration attempt

  • Migration ID: 45071900
  • Attempted: 2026-05-28 ~06:32 UTC
  • Tried twice (once without flags, once with --debug) — both identical failures

Behaviour

  1. dfs/migrations/v2/list-apps returns isMigratable: true; all 4 components marked isSupported: true.
  2. POST dfs/migrations/v2/migrations succeeds; migration 45071900 created; componentsRequiringUids: {}.
  3. Status transitions: INPUT_REQUIRED → IN_PROGRESS → FAILURE.
  4. Final status response:
{
 "id": 45071900,
 "projectErrorDetail": "Your project source code was updated, but the initial build failed. Check the CLI logs or your project build logs, fix any issues and run the migration again.",
 "componentErrors": [],
 "componentErrorDetails": {},
 "status": "FAILURE"
}
  1. No build registered in HubSpot’s project activity (verified via UI and hs project list-builds).
  2. Local source code unchanged (verified via git status). The CLI rolls back its local file mutations on build failure.

Ask

Could a HubSpot engineer pull the server-side logs for migration 45071900 and tell me what specifically failed at the initial-build stage? Empty componentErrors / componentErrorDetails doesn’t give me anything to fix on my end.

Happy to share full --debug output if useful. Deadline-bound — 2025.1 deprecates 2026-08-01, so a working migration path forward matters.

Thanks!

2

Hey @ben-shapiro,

Welcome to the Community!

A few things worth looking into in the meantime:

For the server-side log access you’re after, that’ll likely need to go through HubSpot Support, if you believe this to not be working as expected.

Also tagging in some of our Top Contributors to see if they’ve run into anything similar:

Hey @Anton**, @SteveHTM**, @zach_threadint - do you any experience with platform version migration failures where no component errors surfaced?

Best,

Sam, Community Manager

3

Hi @ben-shapiro :waving_hand:

It might be worth trying the migration on the latest version of the HubSpot CLI (currently 8.8.0).

I hope this proves helpful. Please let me know if you have any follow-up questions.

4

Hi Zach,

Thanks for the steer - upgrading the CLI to 8.8.0 got me noticeably further, so that was the right call.

I re-ran the migration on the stable 2026.03 (not the beta this time):

hs project migrate --platform-version 2026.03

It now gets past the component check and accepts the card as migratable, but fails at the “associate components” stage with a specific component error (previously, on the beta, componentErrors came back completely empty):

Failed to associate components for migration MigrationId{45072120}:
- CARD (sitecore_focus10_card): Internal error encountered while updating project

I ran it twice to rule out a transient issue - identical failure both times:
- Migration ID 45072120
- Migration ID 45072121

Project details:
- Project: HubSpot-OrgChart
- App ID: 38555060
- Portal/Hub ID: 2001761
- CLI: 8.8.0 . Node v25.5.0 . Windows
- Currently deployed: build #25, platformVersion 2025.1 (unaffected by the failed migrations)

A couple of things that make me think this is server-side rather than something in my source:
- The app has two CRM cards, and their JSON definitions are structurally identical (same type: crm-card, location: crm.record.tab, objectTypes: [{ “name”: “companies” }]). The one that fails, sitecore_focus10_card, is simply the first card listed in app.json - so it looks like the migration fails on whichever CRM card it tries to associate first.
- The failure happens entirely server-side: no local files are modified (no archive/ directory is created, hsproject.json stays on 2025.1), so it’s safe to re-run.

Could a HubSpot engineer pull the server-side logs for the card-association step on migration 45072120 (or 45072121) and tell me what specifically failed?
componentErrorDetails only gives me “Internal error encountered while updating project,” which isn’t actionable on my end. Sam kindly offered to route this to Support for the logs - happy to share the full --debug output if that helps.

Deadline-wise I’m bound by the 2025.1 deprecation on 2026-08-01, so a working migration path matters.

Really appreciate the help.

Thanks,
Ben

5

Hey @ben-shapiro,

Thanks for the response on this. To clarify, if you’re having further issues with I would suggest reaching out to HubSpot Support as the community is intended to be a peer-to-peer platform. Since your team has paid plan, I’d suggest calling or chatting in if you believe this to not be working as expected.
Hope this helps point you in the right direction!

Sam, Community Manager

6

This looks like a backend-side migration/build issue rather than a problem with your local source, especially since no component errors are being returned and no build appears in project activity. Hopefully a HubSpot engineer can inspect migration ID 45071900 directly and surface the hidden initial-build failure logs so you have something actionable to fix before the 2025.1 deprecation deadline.