going back to one database if multi-db goes squirly?

gone are the days of my single-user-blog-click-it-and-see approach now I have 10k users and a few hundred blogs on the system!

How easy would it be to go back to the original 1 database if the upgrade to 256 db process goes awry?