By: Rob Reilley, Senior Developer – When migrating content in Sitecore, depending on the source of the data, you have some options. Depending on whether the data you are migrating is from a non-Sitecore site or a Sitecore site, you have some options. Whatever data migration needs you have, Paragon can help you make the right decision and help you implement it.
|Data Exchange Framework||With this Sitecore add-on, you can setup your own custom data importer. There is custom worked involved, but you have the basic skeleton to get started.||Using a recommended Sitecore process to import data.||Needs to be customized in order to import data. Paragon can help with this.||http://integrationsdn.sitecore.net/DataExchangeFramework|
|Custom Importer||With a custom importer, you can fit any kind of data into your new Sitecore System.||Unique to your environment.||Needs to be customized in order to work with the data source. Paragon can help with this.||Paragon can create a custom solution for you.|
|Sitecore Marketplace||There are various Sitecore modules available that you may be able to use to import data.||A variety of modules are available that might work for your environment. Most are easy to install and test.||Some modules may not work with your current version of Sitecore. Also nothing is customized so not all data types or business logic might be supported.||
(CSV file Importer)
(Contains a Sitecore Importer, SQL importer, MySQL Importer and CSV Importer option)
What to Migrate – Anything that fits into the new Sitecore site. Templates should be created before migrating data so content can be matched.
What not to Migrate – Consider leaving out any data that does not apply to the Sitecore site.
|Hedgehog Razl||Razl allows developers to have a complete side-by-side comparison between two Sitecore databases. It highlights features that are missing or not up to date, while giving developers the ability to simply move the item from one database to another.||Backed up by Hedgehog Development. Support and upgrades.||Cost is currently $149, although it may be worth the price for the support.||https://www.teamdevelopmentforsitecore.com/Razl|
|Custom Importer||With a custom importer, you can create a content migration process between different Sitecore Systems.||Unique to your environment.||Needs to be customized in order to work with the different Sitecore databases. Paragon can help with this.||Paragon can create a custom solution for you.|
|Out of the box Sitecore (Packages)||With Sitecore, if you are just copying the same template and data over, a Sitecore Package will work.||Out of the box Sitecore functionality.||No field mapping and package size is limited.|
What to Migrate – Content items, custom templates and images are usually migrated. Also, you should consider anything that was changed in the Core database that you may want migrated.
What not to Migrate – System specific templates and anything that is specific to the previous version of Sitecore. These will mainly be anything that falls under "System".
Make sure you decide to either allow or prevent invalid characters in Sitecore. There is a configuration setting in Sitecore called InvalidItemNameChars that can be used to allow or disallow certain special characters. Also, the order of importing data is important when there are dependencies. Whatever your environment needs in order to import data, Paragon can help shed light on any issues and help you implement a solution that will work best for you.