Once you know what you want to keep, it’s time to run a discovery and gap analysis. This will help you ensure that you have all the data you actually need. Keep in mind that you might not always be able to achieve one-to-one mapping, which means moving what doesn’t fit to distinct areas of the portal.
Once you’ve done the analysis, you can then ensure every call that has to be made of the service layer of the portal has been mapped. With a list of all the data to be migrated and all the calls that must be made, it’s far less likely you will miss something.
Before you conduct the actual migration, it’s good to lay out your timeline of actions that you need to take. Not only will this give you an idea of how long everything will take, but you’ll also be making sure that you don’t miss anything.
The first step is establishing the methodology of migrating your data. Then comes the discovery and gap analysis, followed by data mapping and development.
Then you want to test everything, after which you must make a backup to make sure your information is safe in the event something unexpected crops up.
You’ll then want to do a dry run to ensure no data corruption takes place and no bugs appear. It’s also a good way to figure out how long the actual migration will take.
Have a contingency plan in place, which basically means setting up a way to roll-back to a previous stat and recover your data from the backups. If you don’t know how to do it, you could lose everything. Also, make sure to test your plan for kinks and do a dry run.
After you’re sure that your contingency plan works, you need to stop any new content from being uploaded to your website so that nothing is missed during the migration.
Now, it’s time to do the full migration. Once complete, test the site to make sure everything is operating as it should be and that you have all that data that you wanted. Also, factor in some time in case anything needs to be fixed.
Migration to a new portal isn’t easy, but it can be done successfully as long as you take the time to plan properly. Furthermore, make sure to cover your bases with backups and don’t skip the testing or dry-run phases to ensure that the migration took place without a hitch.