Importing data from your legacy system into your cloud-based Autodesk PLM 360 tenant is a request we hear often. If, for example, you have existing items and bills of materials (BOMs) that are released in the legacy system at certain revisions, you will most likely need them replicated in Autodesk PLM 360. There is a built-in import tool to do just that (among other things). However, there are several ways this tool can be used, and not every way will get you all your desired results. In this video we will guide you through the best approach and usage of the tool for importing legacy data.
In addition to being familiar with Item Detail import projects, you will need to have a well-developed understanding of working versions in Autodesk PLM 360 before launching into a BOM relationships import project that includes what is also called an import of “historical revisions”. Reference the post, “A Close Look at Non-Released Statuses in Autodesk PLM 360” for more information on working versions.
In Autodesk PLM 360, the import tool requires an Excel spreadsheet that holds a BOM structure in one of three types:
1. Level BOM – typically seen in exported data from ERP or MRP systems
2. Hierarchical BOM – most often seen in data exported from CAD tools
3. Parent-Child BOM – BOM data exported from a folder-based system
The import tool of Autodesk PLM 360 supports the Level BOM structure or the Hierarchical BOM structure for importing BOM relationships that include historical revisions.
If you can only obtain data in the Parent-Child BOM format for which you want to import historical revisions, consider running the Parent-Child Excel spreadsheet through a converter to build a Dual-Level BOM Excel spreadsheet that can then be populated with the additional data needed to successfully import all BOM relationships with historical revisions. Razorleaf is happy to provide a sample converter that you can use or modify here: Visual Basic for Applications (VBA) code
Keep In Mind! If you do try to use the Parent-Child format to import revisions, released items will be at a certain released revision but the BOM relationships between items will only exist on working versions. (This problem can also occur if your Level BOM or Hierarchical BOM import projects are not set up carefully). In that case, of course, it means that people downstream from the change process are basing purchasing decisions and the like on unreleased BOMs.
To avoid this situation, reference the video for how to configure the optimum import tool settings. Also limit each import project to 10,000 items due to heavy key match processing for BOM relationships with historical revisions (your total number of items may be much larger resulting in multiple import projects.)
Autodesk PLM 360 offers a robust, extensible product lifecycle management system, and the built-in import tool provides a powerful way to populate data in your tenant. If you would like assistance with your import projects or have questions about the information presented here, please feel free to contact us – we would love to chat with you!