Easier said than done. I had to update the database schema used for storing maps, because it was too simplistic and too limiting. This has been looming for like a month. Once the code was ready I had to put it in production. As you are aware, changing the database schema is not a simple task, and the best way to accomplish it in the pre-beta phase is to drop the database, deploy new code and start again with a clean desk.
I wonder whether somebody could put it next to reasonable steps (well, it all depends on the number of maps, their value and the work required to migrate the database), but what is most important is that it is against mapping principles.
User needs should be first.
Users have no need of doing the same work again.
The data migration is over. You should not have noticed anything but a short maintenance break.
Just in case there is something wrong with your maps - let me know via twitter.