Bundle the tools required for data migration

[mpasumarti]

We are in the processing of migrating from the legacy system Teamcenter to FLC. We are on Teamcenter for over 12 years and we have whole bunch of data to migrate from the legacy system to FLC.

The tools which I used to migrate the data include,

1. Standard Import tool in FLC UI. I have submitted an idea to invoke Import tool in batch mode to facilitate data migration.

2. Tool to upload attachments to FLC.

3. Tool to import BOMs into FLC.

4. Tool to run external scripts on whole items in a workspace or selective items by DMSIDs in a input file.

I created over 100,000 items in various workspaces in FLC, uploaded over 100 GB of attachments and imported over 6,000 single level BOMs as part of this migration. Every time I did one of those activities I had to work closely with the developer of each of those tools to get the issues identified as part of the load fixed to be able to resume the data loading. Instead I felt that Autodesk should have bundled the tools (which are robust) needed for migration and provided to the customer along with the documentation describing various options in each of those tool. By doing this way there is no need for the Autodesk project manager to run around internal resources for the tools to provide to that customer as well as there is no wait for the customer to closely work with the developer to get each of the issues identified in the data load.

[gasevsm]

Thank you for the candid feedback. I would love to hear more specifics about each tool's lesson learned for a chance to enhance them. Without being certain exactly which of the tools you were exposed to, and without trying to make this into a defensive excuse, please understand they are meant as a relatively solid starting point and cover specific or several common ETL scenarios. I've seen first hand when two customers on same legacy system both moving to fusion lifecycle, they both have either configuration differences at the source, data relational differences due to practices that decayed over time, as well as different fusion lifecycle configurations. Their asks of our tools are different then. To me, the most effort in ETL migration procedures is consumed in massaging and preparing for thorough data Extraction, for that drives how much time is spent in the Transformation, which in turn influences the cleanliness and ease of Loading into new system. Being deliberate and disciplined in earlier phases drives most of the success in continuing with the consumption of the data once loaded into the new system. Sorry if this feels a bit philosophical, it is 😉 nevertheless ping me in private to share your story. Would love to use your knowledge to help our future friends migrating into Fusion Lifecycle. Cheers,

[mpasumarti]

Hi @gasevsm,

Thanks for your reply to my post.

I'll be happy to share my experience with each of those tools used to migrate data from our legacy system, Teamcenter to FLC. I am sure (as you were) that identifying the commonly used tools to perform ETL process, standardizing them, bundling them and making them available for future customers would really help both the entities in many ways.

As we are currently in the process migrating the data to FLC to go-live on 12/12/16, I can't convene with you to discuss about this topic. Sorry, for the inconvenience. Could we do it sometime in the week of December 19th?

Thanks,

Madhav

[gasevsm]

Let's target second week of Jan. I'm traveling through to Christmas Day, then taking vacation through New Years.

[benderk]

Thank you for submitting your idea. Have you tried the Modern Interface lately? We request that you review your idea in the context of the Modern interface. If your idea is not addressed, we invite you to create a new Idea in the context of Modern so that it can be addressed accordingly. Sincerely, Keri Bender | Global GTM Business Strategy Manager, Product Lifecycle Management