Best Way to Migrate Source Component Custom Metadata to Tridion
If we are migrating content from the original CMS to Tridion, what is the best way to migrate the customized metadata associated with the components (content) of the original CMS to Tridion? Should we transfer it directly to the sql server or is it possible to transfer it as some xml file etc.?
source to share
You have several options when transferring content to Tridion.
I can't figure out from the above if you're talking about going to SQL Server as an intermediate format or directly to the Tridion database. Importing directly into the Tridion database is definitely not a supported solution and can lead to unpredictable results.
You need to use the API, either the Core Service or the TOM.NET API (if you have Tridion 2011), or the old TOM API if not.
A popular approach is to export all content to XML, which can then be processed using a .NET application.
There are good articles on transferring content to Tridion by Ryan Durkin here and Nuno Linhares here .
source to share
Moving directly to SQL Server is not supported, and the entire system will be unsupported at this point due to potential data consistency issues.
The easiest way is to read data from the source system and use the Tridion API to recreate the item.
If you are migrating metadata, some of the data will most likely fit the taxonomy best, which would mean you want to migrate keywords / structure first, and then tag the content when it hits Tridion.
source to share
As mentioned earlier, going directly to the database is not an option if you plan on using SDL Tridion as the ultimate CMS. In addition to the supported mechanism chosen for Migrate, pay attention to how you are going to structure the metadata in the new CMS, as depending on the scope, structure, hierarchy, relationships between metadata elements, the process can become complex. Also pay special attention to the Blueprint concept as you can probably only merge duplicate values from the old system into one that is inherited.
Don't just think about how to put the metadata into the system and how that metadata will be used and maintained in the new CMS, in this case SDL Tridion
You can also check the latest migration post and plan the migration in general, in case you add more information
source to share