Startup Tip – What I Would Have Wanted To Know About Data Migration

This is the last of a 3 part video series discussing software technologies and data migration. In part 1, I talked about selecting software technologies for your startup. In part 2, I talked about what to do if your existing software technology just isn’t good enough. In this video, I share what I would have wanted to know about data migration before refactoring our software to a new language and platform.

  • ugh…data and databases. We are having trouble with different data storage models as we speak… I’d like to add to document everything becuase even if you might only migrate once, to have that docs on hand if you need to do it again will save so much time.

    in the last month, I’ve moved 3 times from cloud to cloud to cloud. luckily all the same (mysql)…

    Thanks Ross, another great vlog… BTW you look like the godfather in the poster in the upper right corner 🙂

  • Matt – great addition about documentation – very critical to migrating correctly and efficiently. We had a tough time getting our hands around the early migration work because it was not well documented. Good luck with your migration! (as for looking like the godfather…not Johnny Depp, but I’ll take it!)

  • Sharon Zaugh

    Good tip about getting users to test. While it’s easy for developers to give users a rigid list of test scenarios, it’s important to also let users “go off the ranch”. Different minds will find different defects.

    I also find it helpful to have a hardcopy of the data model handy. Mine is a four-page taped together Sybase doc. It travels with me always!

  • Sharon – absolutely true. We did our best to anticipate unusual user behavior in our internal testing scripts, but our users outshined us by doing things we couldn’t predict. A key part of testing…

    True also about having a copy of the data model handy. I can’t say ours travels with us always, but it’s never far away. 🙂

  • Ross, great advice, and I wish I’d had it a while back.
    I was blown away by the complexity and challenges while exploring a data migration from a jsp legacy platform to new php one I was considering last year. While both sites seemed to offer the same functionality to the user, the way each platform structured and used the data (including security processes) was very different.

  • Ric – very true. That’s precisely the challenge we had when we migrated from PHP to Python. We also completely revised our data model, so that contributed to the complexity. When we first modeled migration, we were going to convert in one step, but later, decided we would move the data into neutral tables and then import from there – that step really helped us to focus and reduce errors.

  • Pingback: What programming languages and practices were used to develop Crowdspring? - Quora()

Read previous post:
Startup Tip: What To Do If Your Existing Software Technology Just Isn’t Good Enough

In yesterday's video, I offered five suggestions to help you pick the best technologies for your startup. But what do...