Stuck Migration for Legacy CRM card to new App Card

Developer Support
1

We successfully migrated Legacy CRM Card 563343 to an App Card. Afterwards, we changed the App Card uid and redeployed the project. The deployment removed the original App Card and created a new one. When attempting to migrate again, the UI returns:
LegacyCrmCardMigrationErrorType.MIGRATION_RECORD_EXISTS_FOR_DIFFERENT_CARDS

with
EXISTING_CARD_ID = 104515281

The migration record still points to the old App Card, which no longer exists. Could you clear or update the migration record so it references the new App Card, or advise on the supported recovery procedure?

correlation ID:

019fb7ee-5917-778d-87b3-a24581ee9179

The new CARD_ID after redeployment is 104532160

3

Hey @dish205,

Welcome to the community! :partying_face:

Thanks for the detail on the reproduction steps here – I’ve found a few community threads that might help point you in the right direction:

  1. Deprecating Support for Classic/Legacy CRM Cards

  2. Discrepancy in CRM Cards Visibility for Different Portals (not the same error, but possibly helpful for troubleshooting as it discusses card visibility, objectTypes, card locations, and customized views across)

    Also here are a couple of docs that you might find helpful in the meantime:

I’d also like to tag in some folks from the community to see if they have any tips and tricks on this:

Hey @Mike_Eastwood , @GRajput, @MichaelMa – do you have any suggestions for @dish205 on this?

Thanks!!

Sam, Community Manager

4

Hello,

Thank you for your quick response. However, I couldn’t find a solution for my current issue in the information provided.

It would be greatly appreciated if you could look into this further and provide a solution specific to my current situation.

Thank you for your assistance.

5

Hey @dish205,

Thanks for reaching back out and confirming what you’ve looked into so far. I’ve reached out internally to see if there if this is something we’re able to resolve on our end. I’ll reach back out once I have any updates/ next steps for you!

Best,

Sam, Community Manager

7

Hi @dish205, Try re-running the migration call against the new App Card ID (104532160) with allowDuplicateAppCardIds: true in the request body that flag on the /crm/v3/extensions/cards-dev/{appId}/views/migrate endpoint exists specifically to let you overwrite a stale migration record pointing at a since-deleted App Card ID.

8

Hey @dish205,

Thanks for your patience while I looked into this on our end!

Here’s what I can share: our team has identified the issue with the stale migration and cleaned it up with a fix. You should be able to re-run the Legacy CRM Card to App Card migration against your new App Card ID.

However, I do want to set expectations on one important thing, when the App Card was deleted as a result of the UID change and redeployment, that also removed it from any customized views where the legacy CRM card had previously appeared. Unfortunately, those view customizations cannot be restored.

Once the migration is re-run, the association to the new App Card will be in place and default views will reflect that, but customized views that were affected by the deletion won’t be recoverable.

This is also a good reminder for anyone working with UID changes: as noted in HubSpot’s docs, changing a UID in a subsequent deployment causes the platform to treat it as a new component entirely, which can have unintended downstream effects.

Configure UIDs and initial app features

Keep in mind that UIDs are used as a unique identifier for all your project’s components and features. Once your app or any of its features has been uploaded with a specific UID, changing it in subsequent deployments will force the platform to recognize it as different from previous builds, which may not be intended.

Hope this helps!

Best,
Sam, Community Manager