5 Things You Should Know About the Aras PLM Solution How To Do Better, Faster PLM Data Migrations 
Many (if not most) Aras implementation projects will involve a migration of data from elsewhere into Aras at some point.
Valuable Part, BOM, CAD and Document information may exist outside Aras in other perhaps older business systems, in databases obtained through company acquisition or merger or in previously used PDM or PLM systems.  
Maintaining legacy systems increases IT overheads and obliging people to search multiple systems for information slows down business processes and reduces design & part reuse.
End to End business processes can be made much more streamlined and efficient if product information (data and files) residing in legacy databases can be migrated into Aras.
Here are some examples where the migration of data into Aras can add value;
Migrating drawings from a previous drawing management system
Migrating CAD models from a legacy PDM solution
Migrating Part & BOM information from an MRP or ERP system into Teamcenter so that it can take ownership of these records

Common Migration Challenges
When turning off an old system and moving the data it contained into Aras, it’s crucially important that whatever data people were working with on the previous Friday afternoon is all there, ready and waiting in Aras on the following Monday morning.
If it isn’t or if the data is incomplete or inaccurate there’s usually hell to pay.  So it’s important that the migration is thoroughly planned and stress tested well in advance.
But what are the most common challenges faced by organisations faced with a data migration?
It’s important to begin by distinguishing between the types of data that needs to be migrated because this can impact the complexity of the migration enormously.

"CAD Is Complicated"
On the one hand, office documents can be simple to migrate because they are much less likely to contain links to other documents.  
On the other, CAD models, drawings & assemblies can be much more difficult because of the references between files that are embedded within individual CAD files.  For example, drawing and assembly files will contain references to other CAD models.  CAD models may, in turn, contain references to other associated models or geometry (so called multi-model or WAVE links).
Add to that multiple versions of a CAD file (corresponding to different part revisions) and things can get more complicated.  
And if you need to pre-populate Aras with Parts & BOMs from ERP (prior to Aras becoming the master for those items), that are further linked to the correct CAD item, at the correct revision and at the right status then things get very complicated indeed.

"Where Is The Data Being Migrated From?"
Another factor which can have a huge bearing on the migration challenge is the location of the data to be migrated.
If CAD data is being migrated from another PLM or PDM system it is also likely to be locked away in that PLM system’s vault.  To get it out is not always a simple task because (not surprisingly) making it easy to migrate data into another PLM system is rarely a top priority for the PLM vendors.  
Therefore you will often need the help of a skilled developer with deep experience of that systems API in order to access both the files themselves and the associated metadata which gives the files their context.
And, of course, no two PLM systems work in exactly the same way so it is very likely that the CAD data will need to be manipulated to make sure it complies with the Aras CAD data model.
But at least when moving from another PLM or PDM system, the data is likely to be reasonably well maintained and consistent.  
If you are migrating CAD data from a shared drive or archive, things can get very tricky especially if users have not maintained strict data management rules.
Indeed it is almost always the case that such archives contain inconsistencies in file naming, multiple copies of the same file or assembly references to other files that are not in the archive.
It is essential that such anomalies and errors are fixed before the data is migrated into Aras.  It’s much easier to resolve data inconsistencies earlier rather than later and failure to address issues only serves to weaken the foundations upon which the PLM initiative is being built.
Again to tackle these issues, you will often need the help of a skilled developer with experience of the CAD tool’s API so that the internal references hidden inside the CAD file can be analysed, interpreted and fixed.

How Much Data Do You Have?
Another common challenge is data volume.  Companies will often have thousands or even millions of CAD models, Part records and Documents that need to be migrated.  Moving this amount of data into Aras can be a challenge in itself especially if the migration has to be done to a tight deadline or within a specific window of opportunity.
Having a deep knowledge of how to rapidly and accurately get data into Aras within a specific time period is vital.
Why Choose AESSiS To Help You Migrate Your Data
The AESSiS team have the deep knowledge & experience to help you achieve your migration objectives as quickly and accurately as possible.

We understand how to; 
Extract data quickly & efficiently from other PLM & ERP systems.
Find & analyse CAD data contained in folders and shared drives.
Clean, fix and de-duplicate CAD data before it is migrated into Aras using specialist ShapeSpace geometric search technology.
Manipulate data so that it complies with Aras Part & CAD data model requirements.
Import data quickly & efficiently into Aras.
Manage migration projects effectively via a  tried & tested methodology that ensures issues are found and fixed prior to the final production migration and data is migrated accurately and comprehensively with minimum downtime.

Recent Migration Projects

ANCA - Teamcenter to Aras CAD Migration
Malvern Instruments - CAD data from shared drives into Aras.
ECCO - Teamcenter to Aras CAD data migration
Oxford Instruments - CAD data from shared drives into Aras.
MAN Diesel - Teamcenter to Aras Product Structure replication followed by ongoing synchronisation.
AESSEAL - CAD data from shared drives into Teamcenter.
HMD - Teamcenter 2005 to Teamcenter 2010 CAD Migration (including a database change from Oracle to MS SQL and a selective migration leaving behind unwanted legacy data.