Account migration only moves followers on own instance

[leona-ya]

Steps to reproduce the problem

1. Have an account with many (in this case 150-200) followers, some on the own instance, some on other instances
2. Move the account to a new, fresh account on the same instance
3. See that only the followers on the same instance have been moved

Expected behaviour

All followers should be moved

Actual behaviour

Only followers on the same instance as the accounts have been moved

Specifications

version: 3.5.3 instance: chaos.social

old account: https://chaos.social/@em0lar new account: https://chaos.social/@leona

[leahoswald]

We could fix it by changing the created_at field in the account_migration table to work around the 30 days cool-down period and than run the migration again. Now most oft the followers are migrated but this still looks unreliable and like a bug.

[johann-petrak]

Moving followers did not seem to work at all in my case, though some people have followed again, so it is hard to keep those events separate after a while. Moved from mastodon.social to sigmoid.social

[alakoring]

A similar thing just happened to me. A couple l days ago I moved hosts from mastodon.social to @[email protected] and was following nobody. (I believe everyone who followed me did move over.)

A workaround would be for the server migration to add a sentence telling people to export their list. I had no idea this was needed, and the server migration was so slick that I assumed it was a complete migration.

Sorry if this is a separate issue, I was trying to find an issue and not create a duplicate.

[borisschapira]

@alakoring Hello, I think you're right, I think it's a separate thing, and more a feature request than an issue. The documentation explains that only followers are moved from the old account to the new one.

No other data will be moved automatically Mastodon documentation