🙂 thanks for confirmation that you too agree.

-------------------------------------------------

for the safe side, anyhow you have to take the downtime, no matter which strategy you choose.

So will suggest, to draft your strategy first and then have a test of it(if you have testing environment) and then apply in production.

Moving data from one table to other, dont think will take much time and redefining replication also should not take much time.

In total I cant see more than 2-4 hrs downtime in this case if suggested approached.

PS:- dont worry you improving the things and down time can easily be justified. Good Luck. Also dont forget to take a full backup before starting your activity. Is is just to make sure you can bring the database back to initial stage if anything goes wrong in between.