How to migrate from Mighty Networks, step by step

Members export as a spreadsheet. In Mighty Networks go to Admin, then Members, then Member List, then Download. The file is an Excel (.xlsx) file, not a CSV, and it arrives as a download link by email. The member download requires the Launch plan or higher, so do not downgrade before you have it.

Courses and posts do not export. Mighty has no course or post export, so you rebuild your curriculum from the source files you have, and copy out by hand any posts worth keeping, such as a welcome guide or a resource list.

Timestamps in Mighty's export are in UTC, which matters only if you use join dates for anything, such as anniversary messages or seniority badges.

Mighty organizes a network into spaces with their own feeds, courses and events. Draw the map before you rebuild: which spaces become discussion categories, which become courses, which become learning tracks, and which you retire.

Fewer, busier places beat many quiet ones. If a space has had no posts in two months, fold it into a category or let it go. A new home that feels full on day one keeps people; one with twelve empty rooms does not.

The Switch to HiveLearn wizard accepts the Mighty .xlsx as it is and converts it for you. It classifies the file and maps the columns with AI, and you review the mapping before anything is imported.

For courses, use the course CSV format (Course, Module, Lesson, Content, Video URL) to bring your outline across, then finish lessons in the course builder with video, PDFs, drip schedules and quizzes. For posts you want to keep, a posts CSV (Post, Author Email, Created At) brings them in.

Rebuild the flagship course or program first and launch on it. The rest can follow in the weeks after.

Check one thing before you import: that the email column is complete. Members who joined with a social login sometimes have addresses you do not recognize, and an email you cannot reach is a member you cannot invite. Fix or flag those rows now rather than discovering them during the announcement.

Events are where Mighty migrations slip, because members expect next week's call to happen wherever they look. Recreate every event scheduled after your announcement date in the new calendar first, with RSVPs, reminders and calendar sync, and run live sessions through Zoom inside the community.

Then point the remaining Mighty events at the new home: update their descriptions with the new link and stop creating new events on Mighty. The first live session in the new community is your best migration moment, because it gives everyone a reason to log in on the same day.

Billing does not move across on its own. Plan for each paying member to subscribe again on HiveLearn through Stripe Checkout, paid out to your own connected Stripe account.

End a member's Mighty billing only after they have joined the paid tier on the new side, and say clearly that you will. An early-mover incentive, such as a founding price for the first two weeks, gives people a reason not to wait. Use the exported member list as your checklist and follow up personally with anyone still missing a week before the deadline.

Mighty's strength is its branded mobile app and the sense of place it creates. Be honest about the change. HiveLearn works on phones in the browser and installs as an app from the browser rather than from an app store. Include a two-line how-to: open the link on your phone, then use Add to Home Screen.

A message that works: "On [date] our community moves to a new home with [benefit, such as courses with certificates or a shared events calendar]. Join here: [link]. On your phone, open the link and add it to your home screen so it opens like an app. If you pay monthly, join before [date] to keep your price, and your Mighty billing stops once you have joined."

Some will not, whatever you do. Split them into three groups using your checklist. Paying members who have not moved get a personal email a week before the deadline and another two days before; a direct note from you works better than a fourth broadcast.

Free members who have not moved get the reactivation email and one reminder, then you let them go. They were not paying, and the ones who cared will follow the link.

Paying members who tell you they are leaving are worth one question: why? Their answer is the most useful feedback you will get during the move, and occasionally it reveals something you can fix in the new home before the deadline.

Week 1: map spaces, download the member .xlsx (while you are still on Launch or higher), and set up tiers and Stripe. Week 2: import members, rebuild the flagship course, and recreate upcoming events.

Week 3: announce, open the paid tier, and host the first live session in the new community. Week 4: personal follow-ups, cancel Mighty billing for members who have moved, and close or downgrade Mighty after the last renewal has passed.

Concierge migration is included on HiveLearn's Pro plan and above. On any plan, the wizard can send imported members a reactivation email as a last, clear invitation.

When to stay on Mighty Networks: if a branded app in the app stores is central to your brand and your members' habits, that is a real strength HiveLearn does not match. Move when courses, assessments, certificates or fees matter more to you than the app icon.