Name every category in scope
Ask separately about member identities, profile fields, posts, replies, files, roles, events and payment arrangements. A proposal that says community migration may cover only some of those relationships. Describe the source and destination systems and the necessary member journeys, using the minimum information required for feasibility. Do not send a full private member export merely to obtain an initial discussion of scope.
Resolve plan language in writing
Mighty’s migration FAQ places its migration services on Growth and above, while broader administrative messaging uses migration language around Scale. Treat that difference as a question for a written account-specific proposal. A current price-page feature, an older plan name and an affiliate-program contract are not interchangeable evidence of what your proposed customer plan includes.
Ask how exceptions are accepted
Identify what happens when a member cannot claim an account, an attachment cannot move or a subscription requires separate handling. State who investigates, who communicates with the member and when the transfer is considered accepted. A provider’s completed processing job is not necessarily a complete member experience. Request the expected format of the completion report and known limitations. Keep acceptance deadlines distinct from estimated processing dates.
A fictional scope comparison
One quote offers member and content migration but excludes event reconstruction. Another offers assistance with the next event but leaves older attachments at the source. A club compares those exclusions against its inventory rather than selecting whichever proposal uses more comprehensive language. It retains the exact written scope and quote date, records unresolved questions and postpones the dependent commitment if an essential journey has no workable route. Neither quote is treated as a guarantee that every individual member will participate after launch.
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.
- Mighty Networks migration FAQ — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28
- Mighty Networks administration — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28
- Mighty Networks pricing — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28