Practical guide

Keep the next community event reachable during a platform move

Last materially reviewed 2026-09-28

Quick answerVerify the next real event’s date, timezone, host and join route independently of the general migration.
What to know

Choose the next event as a test

Check the information members need for the next scheduled activity: start time, timezone, location or online route, eligibility and help contact. An archive of past events does not establish future continuity. Do not copy an old event description without checking whether it still points to the right place or owner.

What to know

Check ownership and delivery

Mighty’s event documentation notes constraints around event ownership, including the event creator’s host relationship. Establish who can maintain the event before relying on a volunteer handover. An external meeting link and the platform’s notification behaviour are separate matters. Verify the actual route and avoid assuming that a reminder includes every instruction a participant needs.

What to know

Reconcile old invitations

Decide what happens to calendar entries and notices issued through the old platform. Publish one authoritative correction when necessary and retain a help route for people following an older invitation. Do not silently leave two conflicting events active. A displayed local time should still be checked against the intended source timezone when coordinating participants in different regions.

What to know

A fictional rehearsal

A member opens the upcoming discussion from a phone and finds the correct time but an obsolete meeting link. The host fixes the event route and checks that same member journey again. The group records a repaired event-access issue, not a successful migration of every historical event. The acceptance question is whether the next participant can reach the next activity through the published instructions.

What to know

Before you close this task

Record which account owns the current event and who can correct its practical details. A backup’s ability to post a comment may not include the ability to alter the event itself. Resolve that distinction before the host’s absence rather than discovering it minutes before participants expect to join.

Continue when useful

Next: Absence cover

A named backup needs the right task instructions and permissions before the main host is unavailable.

Open Absence cover →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Mighty Networks events — Merchant documentation · docs.mightynetworks.com · Merchant-controlled · checked 2026-09-28
  2. Member purchase and access — Merchant documentation · docs.mightynetworks.com · Merchant-controlled · checked 2026-09-28