Comments on: Data migration strategies http://itknowledgeexchange.techtarget.com/itanswers/data-migration-strategies/ Tue, 18 Jun 2013 07:20:09 +0000 hourly 1 By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/data-migration-strategies/#comment-71678 tomliotta Wed, 16 Dec 2009 07:44:58 +0000 #comment-71678 Note that whether or not the old and new applications are on the same system or available at the same time will be the major decision elements. Do you know the actual scenario?

Tom

]]> By: flynavy http://itknowledgeexchange.techtarget.com/itanswers/data-migration-strategies/#comment-40731 flynavy Tue, 05 Sep 2006 10:53:28 +0000 #comment-40731 As sheldonlinker stated, moving to Excel is not a great option for this scenario. A lot of data errors can be introduced in a spreadsheet. There are a lot of data migration tools and services out there to assist you with what you are trying to do. I have seen this type of merge done a few ways. You can add the data to the existing database and alter the schema in the migration, you can add the data to a smaller, 3rd database and merge the 2 sources in the migration, or you can migrate the data you have into the new schema and then add the extra data.

]]> By: skeil1 http://itknowledgeexchange.techtarget.com/itanswers/data-migration-strategies/#comment-40732 skeil1 Tue, 05 Sep 2006 08:49:53 +0000 #comment-40732 Have you considered using Access if you must move it to a Microsoft product for user update? At least then it’s databse to database rather than databse to spreadsheet. (Remember the 2 GB file limit in Access.)

]]>