This page is to help you decide if you want to use PDS MOOver to move your ATProto(Bluesky) account to a new PDS. One way or the other. TLDR (You should still read the whole thing), at least read and follow the precautions section.
PDS MOOver is a no frills' PDS account migration tool. Meaning you will find few bells and whistles to simplify the process and hopefully allow more successful account migrations for most users. The creator or host of this tool will not be able to help you recover your account if something goes wrong. So be advised you and your PDS admin may be on your own besides helpful answers and understand the risk you take in doing an account movement. The tool has been tested, and it has worked well, but it is still important to understand this. If you follow precautions section this will also greatly increase the odds of recovering from any issues. You will still need to have some know how, but it is very possible with a backup rotation key and backup of your account. I also recommend trying out an alt before you do your main account so you know what to expect.
Before you even run PDS MOOver I STRONGLY suggest you add a rotation key and have a back up of your repo and blobs. With both of these you are not guarantee a full recovery if something goes wrong. But it will greatly increase your odds.
I recommend using atpairport.com to add a new rotation key to your PLC. or you can follow this blog post to do it with goat. PDS MOOver will not use this rotation key at this time, but if something happens, it helps to have this in the meantime.
I also recommend taking a back up of your account with boat. You want to "Export repository" and "Export blobs". Both just take your current handle and download those exports to your computer. These are your posts, pictures, and videos.
If you're having issues with PDS MOOver first of all, I'm very sorry. I have tested this to the best of my ability, but PDS migrations do come with risks. I would recommend getting with the owner of the PDS and seeing where the account stands with tools like pdsls.
The tool is designed to be able to be re ran IF you set the Advance Options flags.For example, lets say if it created the account, repo is there but some blobs are missing. You can uncheck everything but "Migrate Missing Blobs", "Migrate Prefs", and "Migrate PLC record" and it will pick up after the account repo migration. It is odd in the fact that all the fields are required. That's just to cut down on logic to hopefully cut down on bugs. If you don't ever see the "Please enter your PLC Token" you can just forget about it and call it a day if it's too much. Your old account is still active and working.
PDS MOOver was designed to pretty much be the goat account migration with a UI. Like in this post. Keeping it simple and hard fails if anything goes wrong to hopefully cover most use cases. Rule of thumb if reading the goat migration blog post makes you nervous, you may not want to move to a new PDS with PDS MOOver till it has been battle tested.
Welcome to your new PDS! I recommend now re running the steps in precautions section along with keeping regular backups of your account. With the rotation key and backups you can almost always recover even if your new PDS disappears overnight. It may take a bit of know how, but it is very possible.
Everything happens client side, and the blob uploads take a while. Nothing runs in parallel. Blob uploads happen one at a time; once one is done, the next goes. This is done just to keep it as simple as possible and to hopefully limit the chance of failures on uploads. My personal account takes about 20-30ish mins to move with 1,700ish blobs at 800mb on a 1gig internet connection.
Yep! PDS MOOver is 100% open source and can find the code on tangled.sh. Also, if you're a developer, and you want to fork the code for a new UI. PDS MOOver's logic is all in one js file. Just take it and its dependencies and have at it.