In the past, server merges have been a nightmare for both DBG staff and the impacted players. I propose a slightly different approach which has worked well in my organization. Determine which servers should be consolidated Set up a new, large server to accommodate the players. Front-load more resources than requirements dictate to allow for troubleshooting, data moves, etc. Plan to draw these resources down to levels set by project requirements as allowed. Allow voluntary transfers from affected servers for 8 weeks. These people are your test group. Rewards granted both for early transfer and test/feedback will encourage buy-in. Begin mandatory transfers for an additional 8 weeks determined by alpha-order/guild name in a lead-up to the big consolidation. Reach out to guild leaders and officers with information about how to save their guild decorating layout, and assign trouble tickets top priority during mandatory transfer period. Final consolidation begins 16 weeks after initial transfers began. This will be mostly comprised of characters who haven't logged in for months or years. Free name change service and an XP potion granted to those who lost their character names to active characters, favored to character with highest number of active days played in the last year. This reduces the short-term workload of the team overseeing the transfer, downtime comes in smaller chunks, and long-term workloads are spread further out. This reduces overall efficiency, but also should reduce errors. I wouldn't mind seeing several guilds at end game on my server. Everyone benefits from larger populations.