I followed the directions here yesterday afternoon:
As you can see here, the process seems to have gone correctly. But my follower count on Masto has stuck at 671 since late yesterday afternoon Pacific time. I no longer remember what the original follower count was so I can’t tell you if any of my Masto followers successfully migrated from Masto to Micro.blog.
Please help? Thanks!
I’ve given up on this. I switched off redirect from my Mastodon account. I hope I did not lose followers entirely.
Micro.blog’s lackadaisical tech support is the reason I don’t recommend Micro.blog to more people, and it’s why I’m keeping my eyes open for alternatives.
Email is always the best way to get an answer. Now that we have @sod helping with email support most questions are answered very quickly. The forums here are best for feedback or questions that a lot of people are running into, since anyone can jump in with their own thoughts.
Anyway, back to your question… You still have followers on Micro.blog, so I don’t think the migration worked and I don’t think you lost any followers.
Do you want to try initiating the migration again, or do you want me to manually initiate it? I can monitor your account to see how it goes.
Thanks!
Thank you. I’ll keep that in mind.
I was confused on this point — I saw at least three channels for support: help@micro.blog, this forum, and tagging @help from my blog.
I suggest you need to monitor this forum closely. Because if people see a forum called the “Micro.blog Help Center” it is 100% natural for them to seek help there and for people to get frustrated when they don’t get a timely response.
To be clear: I am (or was) trying to migrate FROM Mastodon TO Micro.blog, and the other way around. Basically, I want to shut down my Mastodon account and move everything over here.
I started the migration Friday afternoon and, when it remained stuck with 671 followers still on my Mastodon account, I canceled it. So now I’m continuing to use both Mastodon and Micro.blog.
Mastodon is now telling me that I have to wait 26 days before doing another migration.
If you can work some magic on your end to speed that along and get it done immediately, that will be great. Otherwise, I guess I’ll just have to wait 26 days to try again.
Thank you again for your response.
Thanks for the clarification, sorry I mixed this up! That 26-day wait is unfortunate. I can’t do anything about it because the migration is triggered from the Mastodon side in this case. (Possibly you could contact the admin of the Mastodon server, but I don’t know if they can reset that either.)
I emailed the admins of the Mastodon server and we’ll see what they have to say.
Thanks!
They can’t reset the countdown clock. No big deal. I’ll revisit this issue in about 25 days. Thanks!