I have absolutely no idea. I just know if you attempt the transfer again you are told you already have a transfer pending.
i wonât put any other through. no b.s.
FWIW ppl in our guild who were doing it like 5 minutes after it went up said they got the error message also and it went away after like an hour or so and says pending. so I would hope that itâs just really backed up
Error messages are put in for a reason. LOL
estimated time to fix that?
successfully touched down in faerlina
how long did it take?
there is a reason it says 4 days. that is the backlog estimation for the transfers. Blizz never updated that system for classic. just be patient
So we should accept these four days without playing just because they donât bother to fix their rotten system?
No, Iâm pretty sure heâs saying that the estimate is based on old servers, meaning it wonât actually take that long, lol.
now its saying 12 hours
it finally says Pending with no errors for transfers yay!
tried to send my character as soon as it went up, got an error message and now it says the transfer is pending altho theres no indicators on the character select screen
somebody did a transfer with more than 25k gold?
Iâve been hearing/reading the gold xfer cap doesnât apply to free xfers. I only have about 22k spread across 4-5 characters though, so idk for sure.
seems like theres no level/gold restriction for the free transfer cause my paladin transfer is in process and it have 34k
Great, I canât even transfer because of the mail bug. Already opened a ticket though.
Transfers are now up to 7 days! If you can get them started.
says 5 days for me on sufuras and canât even log in right now, pretty sick free transfer system
I canât even find the option to xfer my toons. Is this a bug, or am I just not seeing it? Would someone please be kind enough to providea link? Thanks!
UPDATE: The option appeared finally. If anyone else has the same problem I logged out of BNET as well as the game, relogged and the option appeared. I did get an error message but will deal with that later, which seems to correct itself according to other posts and comments here.