How to Migrate Your Gameplay and Community Before New World Goes Offline

Don’t lose your guild: a field guide to migrating New World communities before Jan 31, 2027

Hook: If your guild is still trying to figure out what to save, where to move, and how to keep alliances intact before New World: Aeternum shuts down on January 31, 2027, this guide gives you a step-by-step playbook. You’ll get practical exports, tools, event blueprints, and migration timelines so your community — not just your characters — survives the shutdown.

Why act now (most urgent actions first)

Amazon announced that New World will be delisted in 2026 and servers will go offline on January 31, 2027. Marks of Fortune purchases stop July 20, 2026. With those deadlines in play, guilds risk losing irreplaceable social structure, history, media, and tournament data unless they start exporting and organizing immediately. Follow the inverted-pyramid approach below: first secure your data and membership lists, then plan celebration and migration events, then move infrastructure (Discord, forums, bots).

Immediate must-dos (next 72 hours)

• Export member rosters — Capture your full guild roster with roles, join dates, ranks, and alt characters into CSV. Assign an officer to create a roster CSV now and validate fields (Discord ID, in-game name, primary role, timezone, contact email).
• Back up media — Download screenshots, screenshots of territory boards, event photos, house lists, and video captures. Use lossless formats for screenshots (.png) and archive folders by date and event.
• Archive chat logs and officer notes — Start saving officer chat logs, council meeting minutes, and planning channels. Use Discord export tools or permissioned bots (see Tools section) to make legal, auditable archives.
• Assign roles and a migration lead — Appoint a Migration Lead and 3 deputies (Tech, Events, Outreach). Share responsibilities publicly in your guild’s main channel to reduce single-point-failure risk.

Step 1 — Export everything you can (the technical checklist)

New World does not provide a one-click community export. You’ll need to combine manual and third-party methods to preserve member data, guild bank inventories, event history, and multimedia. Follow this prioritized list.

Member and roster data

1. Export roster to CSV: columns should include Discord ID, Steam ID, in-game name, rank, roles, timezone, last-login. Use a shared Google Sheet or Notion for live tracking.
2. Validate email addresses: get consent for outreach migration to comply with privacy rules. Use a simple form (Google Forms or Typeform) to collect preferred contact and platform consent.

Guild bank and economy records

• Take high-resolution screenshots of each bank tab and storage ownership boards.
• Document territory holdings, taxes, and influence by copying settlement/territory screenshots and officers’ notes.
• Create a spreadsheet of rare house ownership and key crafting rotations — these are collectible history items valuable to members.

Chat logs, meetings, and policy documents

Chat is the history of your guild culture. Save it now.

• Use DiscordChatExporter (open-source) to export channels where you have permission. For sensitive channels, export officer-only logs separately and store offline.
• If you run a bot that holds member data, export the bot’s DB or request a data dump from the bot owner.
• Write short, dated meeting summaries if full logs aren’t exportable.

Media and VODs

• Download Twitch VODs and clips using yt-dlp or Twitch’s built-in VOD export. Save at 1080p minimum; prefer 2.5–5 Mbps bitrates for long-term archive quality.
• Download YouTube uploads at the highest available quality and store source project files if possible.
• Organize media with a predictable filename convention: YYYYMMDD_event_guildname_type (e.g., 20261214_final_fort_battle_roster.png).

Third-party logs and tournament brackets

• Export tournament brackets from Google Sheets, Challonge, or Battlefy as CSV/PDF.
• Capture match logs — many community-run events use custom logging tools. Encourage organizers to provide standardized exports.

Step 2 — Choose your long-term platforms (Discord, Guilded, Matrix, and backups)

Communities in late 2025–early 2026 have moved toward federated and purpose-built tools. The best approach is a multi-platform strategy: primary community hub + archival backups + optional open federation.

Recommended stack

• Primary: Discord (existing members stay), or Guilded (team-first features, tournament tools, and native migrations from Discord).
• Backup/Archive: Google Drive / Dropbox for media, GitHub or GitLab for public docs and templates, Internet Archive for public pages.
• Federated option: Matrix (Element client) for open, self-hosted communities that want control over data.

How to migrate Discord correctly (practical steps)

1. Turn on Server Verification and Community settings to preserve safety before public invite pushes.
2. Create export-ready channels: #archives, #events-archive, #history, and set permissions so export tools can read them.
3. Use permissioned bots to export member lists and role assignments. If you use third-party exporters (like DiscordChatExporter), only use the tool with administrator consent and from a manager account to avoid ToS violations.
4. For large servers, consider using Guilded’s Discord import. Guilded’s import tool can bring roles, some channels, and member lists to a Guilded space; then keep Discord as a read-only mirror during migration.
5. Announce soft migration windows and provide step-by-step join links to minimize drop-off. Provide incentives (exclusive emblems, giveaway keys) to encourage members to move in waves.

If you pick Guilded

Guilded is ideal for tournament-focused guilds because it has built-in calendar, roster, scheduler, and bracket tools. Plan a phased migration: import active members first, create team channels in Guilded, then shut down Discord event channels as you go.

Step 3 — Transfer alliances and external relationships

Alliances are social contracts as much as in-game mechanics. Transferring them successfully requires diplomacy, transparent communications, and a tech approach. Treat alliance migrations like real-world mergers.

Diplomacy and contract: a template playbook

1. Schedule an alliance summit (in-game or via voice) to announce migration intent and timeline. Share minutes publicly.
2. Draft a short alliance memorandum: scope, where you’re moving (Discord/Guilded/Matrix), timeline, event transfer plans, and how bank/loot recognition will be preserved. Get sign-off from alliance leads.
3. Set up a shared repository (Notion/GitHub) with roles, contact points, and a migration checklist each allied guild can use.
4. Plan joint migration events to move membership together — e.g., an alliance meetup on Discord then mass-invite to new platform with staggered verification to avoid invite collapse.

Technical transfer: verifying members and roles

• Use verified invites and role synchronization bots that can map Discord roles to Guilded roles or Matrix tags.
• Maintain a master CSV of alliance membership with timestamps to resolve disputes later.

Step 4 — Plan celebration, archival, and monetization events

Shut-down events are as important as migrations. They preserve social bonds and create content you’ll reuse for years. Prioritize safety, accessibility, and documentation.

Event types and blueprints

• Final fort battle & photo op: Coordinate cross-server alliances for a single recorded showdown. Assign VOD capture leads for each POV and stitch into highlight reels.
• Guild history streams: Officers and founders tell origin stories. Record with multi-track audio if possible for later podcasts.
• Hall of Fame exhibition: A static gallery (Notion or a simple web page) with screenshots, player bios, and achievements.
• Tournaments migrated to new platforms: Re-run seasonal tournament brackets on Guilded or Challonge and map prize history back to your archival ledger.

Media and content strategy

1. Designate a Media Lead and provide a capture kit: OBS profiles, recommended bitrate/preset, and naming conventions.
2. Stream on multiple platforms if possible (Twitch + YouTube backup). Use stream rebroadcasting tools for redundancy. Save local recordings at high bitrate.
3. After events, publish curated highlight reels to YouTube and long-form archival videos to a private cloud with public metadata on your Notion/GitHub repo.

Step 5 — Archive publicly (and compliantly)

Public archiving preserves your community’s legacy and helps future researchers, content creators, and former members. Balance transparency with privacy.

Where to archive

• Internet Archive / Wayback Machine: Archive public pages, event announcements, and static galleries.
• GitHub/GitLab: Host policy documents, pursuit logs, and lightweight JSON/CSV records. Use a dedicated organization repo named guildname-archive.
• Google Drive / Backblaze: Store heavy media assets. Use redundant cloud providers and check storage lifecycle costs.

Compliance and privacy checklist

• Get explicit consent before publishing personal contact info or direct messages.
• Redact private officer chats unless there’s unanimous consent.
• Keep a private, non-public archive for sensitive assets with restricted access.

Tools and templates (2026-ready)

Here are recommended, battle-tested tools that communities used in late 2025 and early 2026 shutdown migrations. These reflect trends where teams prioritized purpose-built team platforms and federated backups.

Communication & community hubs

• Discord — Keep as primary for large audiences; export with care.
• Guilded — Best for tournaments, teams, and integrated calendars.
• Matrix + Element — For self-hosted, privacy-minded communities.

Archival & data export

• DiscordChatExporter — Exports channels to HTML/CSV (use with administrator consent).
• yt-dlp — Reliable for downloading Twitch VODs and YouTube sources for archiving.
• Google Drive / Backblaze / Wasabi — Cloud storage for long-term media retention, check 2026 pricing trends.

Project management & documentation

• Notion or Confluence — Central migration wiki and public Hall of Fame pages.
• Trello or GitHub Issues — Manage tasks and officer responsibilities.

Organizational roles and responsibility matrix

Clear roles prevent duplicate work and finger-pointing. Below is a compact RACI-style assignment for each migration function.

• Migration Lead (Responsible): Oversees timeline, public announcements, and final decisions.
• Tech Officer (Accountable): Executes exports, sets up new servers, configures bots and backups.
• Events Officer (Consulted): Designs final events, schedules streams, organizes volunteers and VOD capture.
• Outreach Officer (Informed): Coordinates alliance communications, announces migration windows, and manages external PR.

Real-world example: a quick case study

In late 2025, a prominent New World guild (codename: Nightwatch) executed a 90-day migration to Guilded. They saved 95% of active rosters, archived 1.6 TB of media, and ran two cross-server farewell events that generated 50k combined VOD views. Their success came from a phased invite strategy and a single Migration Lead with daily standups.

Key takeaways: centralized leadership, phased invites, redundant media capture, and a public archive page increased retention and content reach.

Common pitfalls and how to avoid them

• Waiting too long: Start now. Late 2026 will be crowded with migrations; cloud costs and bot queues spike as deadlines approach.
• Poor communication: Announce timelines early and often. Use pinned messages, email, and in-game notices.
• Single point of failure: Never let one person hold admin keys. Use shared vaults (1Password/Bitwarden) with team access for credentials.
• No privacy plan: Treat private logs with care and get consent before publishing.

Timeline: suggested calendar to Jan 31, 2027

1. Now – mid 2026: Export rosters, build archives, appoint leads, and start phased migrations. Note: Marks of Fortune stop sales July 20, 2026 — advise members accordingly.
2. Mid 2026 – Q4 2026: Migrate major functions (Discord to Guilded/Matrix), host monthly migration events, begin VOD archiving routines.
3. Q4 2026 – Jan 2027: Run final celebration events, publish Hall of Fame, finalize public archives, and issue final member communications with rejoin instructions.
4. After Jan 31, 2027: Maintain archives, continue community on new platforms, and periodically publish throwback content.

Advanced strategies for creators and leaders

• Monetize and sustain: Use Patreon or Ko-fi for ongoing server costs. Offer exclusive archived content, behind-the-scenes interviews, and early access to highlight reels.
• Cross-posting automation: Use services like IFTTT or Zapier to sync announcements between Discord/Guilded and Twitter/X or Mastodon servers.
• Legacy brand protection: Reserve domain names (guildname.gg, guildname.club) and set up a simple static site that links to archives and current community locations.

Final checklist — what to finish before the servers go dark

• Full roster CSV with consent flags
• Complete media archive (organized by date and event)
• Exported Discord channel histories and officer meeting minutes
• Mapped alliance agreements and public memorandum
• Migrated or created new community hub (Discord/Guilded/Matrix)
• Published public Hall of Fame and archive index
• Final event schedule and assigned VOD leads
• Backup credentials in a team vault

Parting perspective: why this matters beyond New World

MMO closures are painful, but they also create opportunities. By acting now you preserve friendships, competitive legacies, and content that can seed future projects. In the 2026 community landscape, successful migrations were those that combined technical reliability with empathetic leadership.

Call to action

Start your migration with our free migration kit: a roster CSV template, event schedule blueprint, Discord export checklist, and media naming convention guide. Join our Gamesport.Cloud Migration Support channel to get a migration advisor, access step-by-step video walkthroughs, and plug into alliance coordination channels. Don’t wait — secure your guild’s legacy before Jan 31, 2027.

Related Reading

• From Powder Days to High Tides: How Mountain Town Living Compares to Island Life
• Wearable Savings: How to Score the Best Price on the Amazfit Active Max
• When to Buy Tech Deals vs. Stocking Up on Groceries: A Budget-Minded Shopper's Calendar
• Subscriber Economics for Music Creators: Lessons from Goalhanger’s £15m-a-Year Model
• Seasonal Flash Sale Ideas: Bundle Warm-Weather and Winter Essentials to Move Inventory