Skip to main content
S
slapha15-Moonstone
15-Moonstone
November 12, 2024
Solved

Experience with Windchill Export/Import and EPMDocuments?

  • November 12, 2024
  • 2 replies
  • 1642 views

Version: Windchill 12.0

 

Use Case: We're looking at a one time migration from one 11.0 system to a new 12.0.2 system, EPMdocuments only


Description:

Does anyone have an prior experience on using this for this kind of use case?

There are multiple options but I'm most curious about the Windchill import/export of containers option.
I have a theory it will fail if there is CAD data used across multiple containers but nothing really addresses that in the PTC support information.

 

I know PLM Connector and Packages are other options, If you have experience with using Packages for this, I welcome any input on that as well.

Mostly trying to get a feel for how well these worked out(or not) for others.

 

Best answer by HelesicPetr

Hi @slapha 

The context import/export is good for some small projects and similar systems also there could be compatibility problem with the target system.

 

Also there is time consuming preparation. You can use it easily for several objects. Nearly always you would need to redefine exported zip and prepare this import pack for target system. Especially the XML files that contain database information. 

 

I did it several times and I always ended with solving issues step by step, one by one.

Problem with revision identification, lifecycle identification,  dtd compatibility between version. ufid identification of any object. 

ufid has to be unique, but if the system already has some data, it is impossible to import. You have to change it in the source files.

 

There are really many issues there that can pop up 😄 and you would not expect it. 

Sometimes it is not logical why the error is shown. 

 

Here is an example snap of the import xml file from the exported zip

You could see that the domain information is there so it has to be also solved.

HelesicPetr_0-1733213489398.png

 

 If you migrate to the new system, there are not so many issues with UFID and it is easier. Also I recommend to use same domain

 

This is my experience that I would say yes it is possible to use it, but first you have to identify all issues that should be solved on a small package of objects.

Then you can use it. but keep in mind, you can no export all in one click. If you have filevaults 1000 GB huge, then you have to split the export to a smaller packs. My experience is that more then 20GB  can case some zippacking/downloading issues. 

 

I believe that there are better ways how to migrate data. For example Windchill packages are better then context export/import where you can set the target system.. Sure you have to know how to configure it. 

. 

PetrH

  

 

 

 

2 replies

H
Hari_Vara16-Pearl
16-Pearl
November 13, 2024

Hi,

WBM is the tailored PTC tool for this. Hope you are using it for this.

Do you face issues in extraction or stating or loading? Hope your Target system is up and running.

Cheers

Hari

    S
    slapha15-MoonstoneAuthor
    15-Moonstone
    November 15, 2024

    Not really an option for us.

    M
    mmeadows-316-Pearl
    16-Pearl
    December 2, 2024

    Sorry, I know this isn't the functionality you are explicitly asking about, but it can do partial data migrations across different source/target Windchill versions.

    Software Factory migrates data using their in-house tools WT-Merge and WT-Validate.  Their solution is older than PTC's Bulk Migrator and isn't tied to DB level migration.  So, your 11.0 system doesn't have to be upgrade to migrate the data into the 12.0.2 target.

     

    Last year we used Software Factory to merge three Windchill systems (10.0, 10.2, and 12.1).  It takes time to do it right, but it went smoothly.  Kicking off a migration from PDM Essentials 12.0 to PDMLink 13.0 this month.  These are all content moves, not container specific.  But, if you can provide a list of what needs to be migrated, they can probably do it.

    HelesicPetr
    22-Sapphire II
    HelesicPetr22-Sapphire IIAnswer
    22-Sapphire II
    December 3, 2024

    Hi @slapha 

    The context import/export is good for some small projects and similar systems also there could be compatibility problem with the target system.

     

    Also there is time consuming preparation. You can use it easily for several objects. Nearly always you would need to redefine exported zip and prepare this import pack for target system. Especially the XML files that contain database information. 

     

    I did it several times and I always ended with solving issues step by step, one by one.

    Problem with revision identification, lifecycle identification,  dtd compatibility between version. ufid identification of any object. 

    ufid has to be unique, but if the system already has some data, it is impossible to import. You have to change it in the source files.

     

    There are really many issues there that can pop up 😄 and you would not expect it. 

    Sometimes it is not logical why the error is shown. 

     

    Here is an example snap of the import xml file from the exported zip

    You could see that the domain information is there so it has to be also solved.

    HelesicPetr_0-1733213489398.png

     

     If you migrate to the new system, there are not so many issues with UFID and it is easier. Also I recommend to use same domain

     

    This is my experience that I would say yes it is possible to use it, but first you have to identify all issues that should be solved on a small package of objects.

    Then you can use it. but keep in mind, you can no export all in one click. If you have filevaults 1000 GB huge, then you have to split the export to a smaller packs. My experience is that more then 20GB  can case some zippacking/downloading issues. 

     

    I believe that there are better ways how to migrate data. For example Windchill packages are better then context export/import where you can set the target system.. Sure you have to know how to configure it. 

    . 

    PetrH

      

     

     

     

      S
      slapha15-MoonstoneAuthor
      15-Moonstone
      December 3, 2024

      Thank you for the detailed reply.

      Terms & ConditionsAccessibility statement