This week's book giveaway is in the NodeJS forum. We're giving away four copies of Serverless Applications with Node.js and have Slobodan Stojanovic & Aleksandar Simovic on-line! See this thread for details.
That's not a lot of data so whatever you choose, it'll be quick.
Since you are migrating between schemas, you need to express how the data should change. While I imagine that data warehouse tools can do this, it seems like overkill for your scenario. I recommend just writing a program to do it.
Well, one approach would be to use an ETL tool like Talend or Pentaho DI (Kettle). For myself, I'd probably dump the single table using mysqldump and load it into the new schema, use a set of sql commands to plunder it into loading the new tables, then drop the copy of the original single table when everything's been place in its new home. For best results, don't index or set foreign keys until AFTER all the new tables have been loaded.
When it comes to destroying a civilization, gas chambers cannot hold a candle to echo chambers.
Mo-om! You're embarassing me! Can you just read a tiny ad like a normal person?
global solutions you can do at home or in your backyard