Skip to main content
oleksii_9242
Participant
March 18, 2026
Question

Custom Metadata Changes After Converting InDesign Files from v15 to v20

  • March 18, 2026
  • 2 replies
  • 96 views

After converting some old .indd files to v20 from v15 I see that custom metadata is completely wrong. I’d assume that during conversion InDesign finds old metadata packets and set incorrect values 
Here is the cimpress:Id value we have before conversion which is correct

But after conversion to v20(v19 works correct) I got something like this:

Is it possible to fix conversion process somehow, because it breaks a lot of flows and makes migration to the new InDesign versions impossible?

    2 replies

    Abhishek Rao
    Community Manager
    Community Manager
    March 18, 2026

    Hi ​@oleksii_9242,

     

    Thanks for sharing the details. I understand how this could disrupt your workflow, especially when migrating files across versions.

    I’d suggest trying the recommendation shared by the expert to check if any scripts or plugins might be modifying the metadata during the conversion process.

    If the issue still persists, could you please share a sample file from the v15 version so we can test it on our end. If the file is confidential, you can share it via DM on the community using a public cloud platform like Google Drive or Dropbox.

     

    Let me know how it goes, and I’ll be happy to assist further.

    Abhishek

    oleksii_9242
    Participant
    March 20, 2026

    Hi, Abhishek, you can find this file it attachment, called “BEFORE_CONVERSION.indd”

     

    Abhishek Rao
    Community Manager
    Community Manager
    March 20, 2026

    Hi ​@oleksii_9242,

     

    Thanks for sharing the files, I really appreciate it. I tested them on my end and was able to observe the same behavior, where the metadata changes in InDesign 2025 and 2026 compared to 2024.

    I also noticed a prompt while opening the original file indicating a missing plugin, “VP.CONTENT.AUTHORING.INDESIGN.PUEBLOOBJECTMODEL.PLN.” This could be related to how the metadata is being handled during the conversion process.

    I’m checking this further with the product team and will keep you posted as soon as I have an update.

     

    Thanks for your patience. 

    Abhishek

    Legend
    March 18, 2026

    Sounds like a custom / third party namespace.

    Watch out for a script or plugin - especially by that third party - that detects the document conversion and decides the document is a different resource worth another ID.

    oleksii_9242
    Participant
    March 20, 2026

    I’ve tried and checked everything, furthermore I opened broken file in HEX editor and was able to find parts of old metadata packets with wrong data, there are no way to view this old packets except HEX editor