7 Replies Latest reply on Oct 26, 2018 3:39 PM by John Matrishon

    Any issues with self-Migration of design data from WorkgroupPDM to PDMStandard

    Steve Hopla

      Hello all:

      Has anyone had issues moving (checking-in) their design data when going from WorkgroupPDM to PDMStandard. We are upgrading to PDMStandard and I am wanting to check all our files (parts, assemblies, drawings) into our new vault. I do know that the new files that are checked into PDMStandard will not have the history (old versions/revisions). Our total vault data (under 1GB) is not very large. Thanks.

        • Re: Any issues with self-Migration of design data from WorkgroupPDM to PDMStandard
          Matt Peneguy

          If you are on subscription, put in a service ticket with your VAR.  Since you aren't going to be moving the different revisions, they should help you for free, IMO.

          Since you are moving everything over "en masse" and you don't need the old version, like you, I think there shouldn't be anything to it.

          • Re: Any issues with self-Migration of design data from WorkgroupPDM to PDMStandard
            Nadia Shea

            If your vault is that small, do the following:

             

            • Create a new local 'working' folder on a Workgroup PDM client.
            • Do a Get Latest on the entire Workgroup PDM vault.
            • Copy it over to a PDM Standard local vault view
            • Check it in.

             

            Here's where this method can fall down for you or for Workgroup PDM Vaults that are much larger.

            • If you have duplicate files in the Workgroup vault with same name. Since Workgroup PDM caches everything locally to a monolithic folder and does not recreate the Workgroup Project structure within that working folder, you're only getting one copy of the file. If the geometry is vastly different between those duplicate name files, this is going to create a lot of strange looking assemblies.
            • The files will be dumped into one big folder and need to be sorted and organized afters. Do this AFTER it's copied/checked into new vault so PDM has a change to manage the references.
            • Checking in this much data or a larger amount can choke the limited resources SQL Express has access to and it can take longer than you expect.
            • Check in should be done in one big go. Trying to check in 'batches' of files (to avoid above point) can cause other references issues, especially if assemblies/drawings are checked BEFORE the referenced parts/subs.

             

            If your data is really only a GB or so, it might be easier to:

            • Identify your top level assemblies in Workgroup PDM (Hopefully it's a small enough number to make this less cumbersome)
            • Open each top level up in SOLIDWORKS/SOLIDWORKS Explorer and Pack and go (include drawings) to the PDM Standard vault view (preferably sub-folders), then check them in.
            • This method WILL create duplicates if multiple top level assemblies use the same part file but that can be cleaned up once it's in the vault.

             

            Either method can be used for self migration but have their own cons and require some level of qualitative clean up.

             

            Resellers really stay far away from this kind of task via support, even with such a small amount of data, not because we're money hungry capitalists, but because of liability. We don't want to be lambasted later on if data integrity is found suspicious. This is your production work. Resellers have to protect themselves from any potential accusations of loss of productivity. Data migration services are at cost because we spend a lot of time upfront understanding your data and it's usage, gather all the legacy data (quite often design library, toolbox, or other random folders of stuff NOT in Workgroup PDM),  write/configure custom tools to move your data, often write/configure custom tools to add valuable data during the migration, and guarantee the data integrity is preserved during/after the migration.

            • Re: Any issues with self-Migration of design data from WorkgroupPDM to PDMStandard
              John Matrishon

              How important is that history in PDMW to you?   If you only want the latest, I'd go with what Nadia suggested, but losing that history even in a small vault can really create mysteries down the road.   Many VARs have different migration tiers, so you might be able to get a lower tier and keep your history.   It takes time, but best to really prepare and do the homework, because once you start down a path it may difficult or impossible to start over.

              JM

              • Re: Any issues with self-Migration of design data from WorkgroupPDM to PDMStandard
                Nadia Shea

                John makes a great point.

                 

                Self-migration, no matter what method used, is limited quite often to latest version. (Technically not impossible to self migrate ALL versions but so cumbersome it's basically impossible)

                 

                Any VAR or PDM service provider can give you options on migration. In order, the cheapest to mostly costly options are:

                • Latest VERSION (note: this is not necessarily the last approved revision), all or partial project folders.
                • All versions, All or partial project folders.
                • Some versions (most common example: Latest 'REVISION' or latest # of 'REVISIONS'), all or partial project folders.

                That last option can bump a migration project multiple factors higher in time, effort, and cost, depending on source data.