Prismm/AllSeated Is Shutting Down: What to Do Now

If you planned a wedding, corporate gala, or other event on AllSeated in the last decade, you probably have muscle memory for its floor-plan tool. That tool doesn't exist under that name anymore, and soon it won't exist at all. AllSeated rebranded to Prismm, Cvent bought it, and Cvent is shutting the standalone platform down. Here's what's actually happening and what to do about it before the lights go out.

What we know about the shutdown

Cvent acquired Prismm (formerly AllSeated) in 2025 and announced it's retiring the standalone platform on December 31, 2026, folding customers into Cvent's own Event Diagramming tool (the former Social Tables). The wind-down happens in stages, not all at once:

• July–September 2026: accounts lose the ability to create new events, rolling out account by account.
• October 1, 2026: the platform goes view-and-export only — you can look at existing floor plans and pull data out, but you can't design anything new.
• December 31, 2026: prismm.com access and support end completely.

Two details matter most: templates, favorites, and saved object groups don't carry over automatically to Cvent's replacement, and Prismm's floor-plan files don't import into most competing tools. Guest lists export cleanly as CSV; seating layouts don't — moving those means rebuilding, not transferring.

Sources: PlanSeats' Prismm shutdown comparison and Floors.live's Prismm migration timeline both confirm the October 1 view-only cutoff and the December 31, 2026 close date.

Step-by-step: export your data before October 1

Do this now, not in December. Once the platform locks into view-only mode you lose the ability to reconfigure anything, and after December 31 you lose access entirely.

1. Export your guest list as CSV. In Prismm, open Reports, set the Report Type to Guests, configure the Fields you want (name, party size, RSVP status, meal choice, table assignment), click Generate, then Export to CSV. Do this for every active event — it doesn't carry over between events automatically.
2. Export your floor plan as PDF or image. You won't be able to re-import this into most other tools, but you'll want the visual reference while you rebuild — table numbers, room layout, and where doors, dance floor, and head table sit relative to guest tables.
3. Write down table shapes and seat counts separately. A CSV won't tell you that Table 4 is a 72-inch round seating 10 or that Table 9 is a king's table seating 20. Make a simple list: table number, shape, capacity. You'll re-enter this manually in whatever tool you move to.
4. Pull your seating rules out of your head (or old notes), not just the software. Prismm doesn't export "keep together / keep apart" logic in a reusable format. Before you forget which constraints mattered, write them down as pairs: who must sit together, who cannot share a table, and any VIP or head-table rules (wedding party, sponsors, officiants, honorees).
5. Save any client-facing exports you've already sent — floor plans, escort card lists, place card data — as your fallback if the rebuild takes longer than expected.
6. Pick a replacement and re-enter tables, seat counts, and rules first, guests second. Getting the room right before you assign a single guest saves you from redoing the layout twice.

What actually matters to carry over

Not everything from a Prismm event is worth rebuilding. Prioritize, in order:

1. Table shapes and seat counts — this is the skeleton of the whole chart and the hardest thing to reconstruct from memory later.
2. Keep-together / keep-apart rules — divorced parents, feuding coworkers, the two guests who requested to sit together. These are almost never written down anywhere but the old software.
3. VIP and head-table assignments — sponsors, honorees, wedding party, executives. Get these locked before you auto-seat everyone else.
4. Guest list with RSVP and meal data — this is the one thing that exports cleanly as CSV, so it's the least urgent to protect manually.

Honest comparison of replacements

None of these are a perfect drop-in for Prismm's full event-design suite (3D rendering, AV diagramming, room measurement). If all you need is guest and table seating — which is most weddings, galas, and dinners — here's how the realistic options compare:

PlanSeats is marketing itself hardest as the direct Prismm replacement and has migration content built for exactly this moment, which is worth a look if you want something closest in spirit to Prismm's client-collaboration features. SeatPlan.io and PerfectTablePlan are the longer-standing options — PerfectTablePlan if you want a one-time desktop purchase and don't mind installing software per machine, SeatPlan.io if you want cloud access without a recurring fee for a single event.

If you're planning one event and don't want a subscription at all, that's where Seatwise fits: it's free to lay out tables, paste your guest list, set keep-together/keep-apart rules, and auto-seat, with a single $12 payment per event to export the floor plan, per-table lists, a printable "Find your seat" board, and an escort-card CSV. Nothing uploads to a server, so there's no re-run of the "where does our data live" conversation you may already be having about Prismm.

For corporate planners and venues running many events

If you're a planner or venue with a dozen-plus events a year on Prismm, the calculus differs from a single couple migrating one wedding — see our table math guide if you're rebuilding layouts from scratch and want a starting point for table counts.

1. Volume math changes the pricing comparison. A per-event flat fee (SeatPlan.io's £8, Seatwise's $12) is cheap for one event and adds up across dozens; a monthly or annual plan (PlanSeats Pro at $39.99/mo, SeatPlan.io's Event Manager at £35–40/mo, or Seatwise's Planner licence at $49 a year for unlimited events with your name and logo on every export) usually wins once you're running more than three or four events a month.
2. Reusable venue templates matter more to you than to a couple. If you run events at the same venue repeatedly, prioritize a tool that lets you save a room layout once and reuse it — check this explicitly before committing, since Prismm's own templates don't migrate automatically to anything, including Cvent's own replacement.
3. Export formats decide who gets paid on time. Confirm any shortlisted tool exports per-table guest lists in a format your catering and AV vendors already accept (CSV, PDF) — don't assume parity with what Prismm produced.
4. Start the migration with your highest-volume upcoming events, not chronologically. Rebuild the layouts for your next three events first, in whatever tool you pick, rather than trying to migrate your entire historical event library — most of that is archival and doesn't need to survive the cutover.
5. Get quotes and trial multiple tools before October 1, while Prismm is still exportable, so you have your CSVs in hand for a clean side-by-side test rather than doing it under deadline pressure in November.

The deadline that actually matters

October 1, 2026 is the real deadline, not December 31. Once Prismm locks into view-only mode, you can no longer create or edit anything — you're just reading what's already there. Get your guest CSVs, table lists, and seating rules out before then, and the December 31 close becomes a formality instead of a scramble.