Hi Daniel,
This is a known NuCache issue others have hit the exact same stack trace during migration. A few things to try:
1. Find the problematic node (https://our.umbraco.com/forum/using-umbraco-and-getting-started/109590-boot-failure-nucache):
sql
SELECT TOP 10 nodeId, LEN(data) as dataLength
FROM cmsContentNu
ORDER BY dataLength DESC
If any row is 1M+ characters, clear that entry and delete App_Data/TEMP/NuCache/ before retrying.
2. If that doesn’t fix it (https://our.umbraco.com/forum/using-umbraco-and-getting-started/109590-boot-failure-nucache), also check umbracoDocument / umbracoNode for broken records — someone hit the same error where cmsContentNu wasn’t the issue and tracked it down to 5 specific nodes there.
3. To get past v8 temporarily (https://github.com/umbraco/Umbraco-CMS/issues/12103), disable local DB entirely to force loading from the database instead:
xml
<NuCache IgnoreLocalDb="true" />
The reason staging worked but production didn’t is almost certainly a specific content node added in the last 4 years.
Note: This answer was created with the assistance of AI and is mostly correct please verify against the linked references.
EDIT: Daniel himself came back with the actual root cause and a great solution worth highlighting: