Facebook groups migration: UK step-by-step guide

What to take away

Facebook groups migration is not a one-click transferavailable Facebook downloads are files, not a ready-made community. Plan to rebuild structure, rules and history.
If your organisation decides how to use exported personal data, settle the lawful basis before importing it.
Choose a destination and check its import options before preparing member data.
The group itself is your only reliable channel for telling members, so announce the move there.
Allow four to six weeks for a group of a few thousand members, and keep the old group read-only during the switch.

What the export does and does not give you

Facebook does not provide a one-click transfer into another community platform. As a group admin, open the group's settings and check whether Download Group Data is available; download only the data Facebook makes available there. For your own account data, go to Settings & privacy > Settings > Accounts Centre > Your information and permissions > Download your information, choose HTML or JSON and request a copy. That personal account download is not a complete export of every member's data. Treat any export as raw material rather than a community you can copy across.

What the export contains

Travels in the export

Member list: Yes
Post and comment text: Yes
Member relationships: No
Rules in your head: No
Reasoning behind old bans: No

Does not travel

Member list: No
Post and comment text: No
Member relationships: Yes
Rules in your head: Yes
Reasoning behind old bans: Yes

The relationships between members, the rules you carry in your head and the reasoning behind old bans do not travel in a file. Someone has to write those down again.

Choose a destination and check its import options

Discourse, Circle, Mighty Networks and Disciple are possible destinations. Discourse is forum software, while Circle, Mighty Networks and Disciple are hosted community platforms. Compare discussion format, moderation controls, member access, data export, accessibility, integrations and the admin support you need. Ask each provider to confirm whether it can import your available Facebook files and what migration support is included.

For member records, prepare a UTF-8 CSV only from data you are entitled to use. Map source columns to fields the destination accepts, such as name and email, and leave out data the platform does not need. Posts, comments, reactions, bans and relationships may need to be rebuilt or kept as an archive; do not assume they will import. For Discourse, check whether its official import scripts support your source. For other destinations, ask the provider about supported CSV imports and migration services, and get a current quote before choosing.

Settle the lawful basis before the export lands

If your organisation decides why and how to use exported personal data, it is the controller for that processing. The UK GDPR applies, alongside the Data Protection Act 2018. Treat access, security, retention and individuals' rights as your responsibility from the point you obtain the files.

Lawful basis before the export lands

Confirm you are a controller of the data
Name the lawful basis for the new platform
Give notice and a way to decline
Set the retention period for the raw export
Read ICO guidance before deciding
Check processor questions with your vendor

A lawful basis must fit the purpose for which you use the data. If you rely on legitimate interests, document your assessment and explain the change to members; a move to a new platform may change their expectations. Do not treat silence as consent.

Use the ICO's Lawful basis interactive guidance tool to help choose a basis. If you rely on legitimate interests, document a legitimate interests assessment. Check the ICO's data protection fee self-assessment to see whether your organisation must pay the fee, and set a retention period and process for member rights before deciding how long to keep the raw export.

Our guide to data protection rules for community software covers the processor questions you will face once a vendor holds the data.

Run the migration in eight steps

Write the privacy notice for the new platform before anything else moves.
Name the lawful basis and the retention period for the export.
Download the group data and store it in one folder with access limited to named staff.
Check every member record you plan to import against a notice or consent record.
Set up the new space: categories, welcome post, rules, moderation rota.
Invite members in batches, with one link and one explanation of what changes.
Run the group and the new platform in parallel for a set number of weeks.
Make the group read-only, then delete the raw export once the retention date passes.

Tell members in the place they already are

A pinned post and a short series of reminders over a fortnight will reach more members than a single announcement. Explain what changes, what stays the same, and why the move is happening.

Do not import email addresses collected for another purpose and call it consent. Group membership does not create a marketing permission.

Give people a route to say no and a way to have their data removed, and record both. Those requests are the first test of whether the new platform can honour the promises in your notice.

Rebuild moderation before you invite anyone

The Online Safety Act 2023 applies to regulated user-to-user services, with Ofcom as the regulator. A hosted group does not automatically make its owner a regulated provider: assess which organisation provides the service and whether it has UK links. In-scope providers have duties that include assessing illegal-content risks; additional duties apply where a service is likely to be accessed by children.

Use Ofcom's online safety guidance for providers to check whether the service is in scope and what risk assessments, records and other duties apply. Do not assume a generic moderation rota is enough.

You also need a rota, an escalation route and a written rule set that survives the move. Members will test all three in the first week.

Common questions

Can we move members to a new platform without asking them?

Do not assume group membership permits you to move someone's data to a new system. Confirm the lawful basis for the new use, tell members what will change, and invite them to join rather than silently enrolling them. Offer a clear way to decline and request removal.

How long does a Facebook Groups migration take?

For a group of a few thousand members, four to six weeks from the first notice to closing the old group is realistic. The technical move is quick. The records and the moderation rebuild are not.

Do we lose our search traffic when we leave Facebook?

Some, yes. Posts in a Facebook Group can rank in search results, and that visibility does not transfer. Weigh the loss against the control you gain before you set a date.

What should happen to the original group?

Keep it open and read-only for a set period so late members can find the new address, then decide whether to close it. Announce that decision on the same day you make it.