Download The Guide to Data Migration Projects: http://www.cloveretl.com/data-migration/guide. Data migration projects require (and deserve!) proper planning. To help you get going, we’re breaking down the 13 most important stages.

1. 13 STAGES
of a SUCCESSFUL
DATA MIGRATION
Defining the Scope Finding Teams & Resources
Planning
Data Discovery
#1
#3
#4
#5
#6
#7
#8
#10 #11
#12
#13
#9
Work with a minimal data set for the migration,
but don't lose the big picture. The migration likely
coincides with a larger plan of data connections
between systems, so don’t forget about them.
Plan for "always complete deliveries." Split the
workload into standalone phases (milestones)
that can be presented to users and tested
independently and viewed as complete.
And, of course, always have a Plan B!
This tracks alongside #3. You can hardly
establish a realistic plan without understanding
the data you're dealing with. You need tools and
expertise to analyze the actual contents of the
data. Only then can you fully cover the whole
extent of the project.
Budget
Understand your scope and determine the
involvement of your tech teams and external
contractors. Who’s managing the project? What are
the external resources billing you for and what are
you signing off on?
Milestone Start
Ensure that everyone clearly understands the scope,
goals, and planned deliveries for each milestone.
Remember: "Always complete" deliveries!
Forget fixing data in Excel!
That would be your last resort.
A repeatable migration process is
the key to success, so work towards
as much automation as possible.
ImplementationReiteration
You WILL have to go back and change
things. You WILL have to redo some parts.
Migrations are prone to scope adjustments
and depend on changes in the target
implementation and on the human factor.
Milestone Testing
Get everyone on board with testing regularly. Don't wait to
pull the curtain; be transparent and test as often as you can.
ALWAYS test on the full data set.
Project Sign-off
All milestones met? No more calls
for one last iteration? Well, there is
one more—the final one. Make sure
everything is tested and that you've
got a checklist of actions required
for go-live handy.
Ongoing Data Integration
So you've switched over to the new systems and all is well. Congratulations!
Now we can tell you the big secret: the migration was just a warm-up. The real fun
begins with the new system in place. Go back to the big picture and imagine all the
data that will need to be connected on a continuous basis, be it real-time
synchronizations or regular offloads to some BI or analytics storage platform.
Contingency
No matter how hard you try, and no matter how much you test, there's
always going be a moment when you realize you missed something.
If you’ve worked towards having automation and a solid method for
repeatability, omissions should be simple to manage.
Go-live
It’s the big day! Or is it? If you’ve
kept true to designing repeatable
automated processes that take care
of most of the data heavy lifting, this
will just be “another run.” If not,
don't forget your rollback plan!
You need close cooperation from business
leads who deeply understand the system in
question. Make sure to secure access
permissions for the implementation team.
#2
Moving years worth of data from your old CRM, ERP or HR system to a
new one? Or moving to a more powerful infrastructure? Data migration
projects require (and deserve!) proper planning. To help you get going,
we’re breaking down the 13 most important stages.
Data Integration www.cloveretl.com
We discuss these project stages in much more depth in
The Guide to Data Migration Projects
Download it for free at www.cloveretl.com/data-migration/guide
We discuss these project stages in much more depth in
The Guide to Data Migration Projects
Download it for free at www.cloveretl.com/data-migration/guide