Hello @GreeshmaReddy
Haha, you've started something fun! Let's delve deeper into this.
The best place to start is actually back on the Data Center side inside the Confluence Cloud Migration Assistant (CCMA). Check your old migration plan or the pre-migration checks there.
CCMA has a specific missing-attachments check that outputs a handy CSV showing exactly what was broken or missing on the source side before the move even started.
You'll want to verify if those specific files actually exist in your Data Center attachment directory and ensure the Confluence system user has the proper read permissions to access them. If the files were moved, renamed, or are just broken links in the database, the tool will just skip them.
Don't waste time trying to patch this up on the Cloud target. It's much cleaner to fix the source-side attachment or permission issues first, wipe the sandbox, and rerun the migration. If you've already completed the move and can't find the logs, open a ticket with Atlassian Support right away. Give them your migration plan ID, the affected space keys, and a few example page URLs so they can dig into the backend migration logs and tell you exactly why those files were left behind.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.