The Questions Official Documentation Leaves Open
The most useful non-price question is often not “Does this platform have feature X?” It is more specific: Can I perform this operation, under this condition, with this data, and what happens next?
That is the question official documentation can answer—or leave open. A page about inviting members is not automatically a page about moving paid subscriptions. A page about exporting email addresses is not automatically a promise that posts, direct messages, media, and payment records are portable. An API landing page is not automatically a statement about every resource or event.
“Not recorded” is not “unsupported.” It means the reviewed official material did not answer the exact question at the same scope. It is not a claim that the provider lacks the capability.
Read the blank before reading the feature name
This article records conditions stated by the providers in public pricing, help, and developer documentation. It does not test the products or turn a missing sentence into a product verdict.
What the reviewed documents answer
Each column is a broad due-diligence topic, not a normalized feature or a comparable coverage score. Read the provider's named object and conditions in every cell. “Documented” includes an explicit statement that an option is unavailable; “Different scope” means a nearby operation is documented instead. “Not recorded” means the reviewed material did not answer the requested operation at the stated scope.
| Provider | Custom domain | Member or contact export | Public API or webhook | Paid-member or subscription migration |
|---|---|---|---|---|
| Skool | Not recorded No current official document at this level of detail was identified in the reviewed help center. This is an unanswered question, not a non-support finding.
| Different scope The official help page documents exporting Membership Questions answers, but does not establish a general member-list export.
| Different scope The Plugins page documents Pro Zapier integration and a developer-only invitation webhook; a general public API is not recorded at the same scope.
| Different scope The official invite page documents bulk CSV invitations for old customers or members and says they receive access without purchasing; it does not answer whether paid subscriptions can move.
|
| Circle | Documented The help center documents custom root-domain setup, DNS records, and the redirect from the default community address.
| Documented The help center documents CSV export for the community audience and other audience areas, with member and non-member fields described.
| Documented Circle documents Admin, Headless, and Data API offerings, plus plan-dependent API tokens and workflow webhooks.
| Documented The paywall migration guide documents moving third-party paid members with trial subscriptions, invitations, and a separate migration-service path for eligible payments.
|
| Mighty Networks | Documented The developer documentation describes Custom Domain Mapping and the Launch Plan or higher condition.
| Documented The documentation describes downloading a network member list and separate space and plan member lists, including the listed fields.
| Documented The Admin API documentation describes programmatic access to members, content, events, and webhooks.
| Documented The migration guide says paying members cannot be transferred directly or have accounts created for them, and gives a free-trial transition as the recommended path.
|
| Podia | Documented The help center documents connecting a custom domain with a CNAME record and explains what happens when the domain changes.
| Documented The help center documents exporting all contacts or selected contacts as CSV, and describes a separate product-customer export.
| Documented Podia explicitly says it does not offer a public API or webhooks and points to Zapier as a workaround.
| Documented The migration guide documents product migration and customer import, while explicitly excluding payment plans, subscriptions, and payment details from migration.
|
| Heartbeat | Documented The help center describes using a custom subdomain for the community and connecting it through Entri or DNS records.
| Documented The help center documents a support-requested community export as a ZIP of CSV files and separately identifies the member list and several content categories not included.
| Documented The help center documents an API key and links to API documentation, while stating that chat and voice channel data are not currently available through the API.
| Documented The Circle import guide distinguishes people and content from paid subscriptions and points to a separate subscription import for active subscriptions.
|
| Patreon | Documented The help center documents connecting a custom domain to a creator page, including root and subdomain options.
| Documented The help center documents exporting audience emails and distinguishes filters for paid and free members.
| Documented The developer reference documents campaign, member, post, and webhook endpoints.
| Different scope The official beta page describes importing an existing email list into free membership; it does not answer whether active paid subscriptions can be migrated.
|
Documented — The reviewed official material answers the question or explicitly says the option is unavailable.
Different scope — The reviewed material describes a neighboring operation, not the question in this column.
Not recorded — No same-scope statement was identified in the reviewed official material.
The displayed source records were checked through 2026-09-01. The verification method identifies how the public source was retrieved; it does not claim personal product use.
When the reviewed sources both state a condition but do not line up, see the companion guide to handling official source conflicts. That is a different evidence state from an operation that remains unrecorded.
The table uses these evidence states. Documented means the reviewed material answers the question, including an explicit statement that an option is unavailable. Different scope means the source describes a nearby action but not the requested operation. Not recorded means no same-scope answer was identified in the reviewed material.
That distinction matters because the words used by each provider are not interchangeable. “Community,” “member,” “contact,” “customer,” “plan,” and “subscription” can name different objects. The table keeps the source’s object and condition attached to the claim instead of flattening them into a universal yes-or-no field.
Questions that look similar but are not
Can the community use my domain?
“Custom domain” can mean a root domain, a subdomain, or a branded address with a separate DNS and redirect setup. The operational question is not just whether the phrase appears. Ask which kind of domain is supported, which plan or creator-page condition applies, what changes for the default address, and whether sign-in or existing links are affected.
An unanswered or different-scope entry should remain a question for the provider. It should never be rewritten as “custom domains are not supported.” The source does not justify that leap.
Can I take my people and data out?
An export can cover a member list, contact fields, product customers, or a community archive. Those are useful but different scopes. An export page may also name exclusions or require separate steps for data not in the main file.
Ask: Can I export the complete member or contact list for my plan, which fields are included, and where are posts, direct messages, media, and payment records handled?
This question is more useful than a single “export available” label because it tells the provider exactly which boundary remains unresolved.
Is there an API or webhook for my workflow?
An official API document can still be limited by plan, authentication mode, resource, event, or client-versus-admin scope. A webhook can automate a narrow event without being a general API. A third-party integration can also be a separate path rather than evidence of a public API.
Ask: Is the interface a public, admin, member, or integration-specific API; which resources and events are available; and which plan and authentication conditions apply?
The table records those distinctions where the sources make them. It does not turn the resulting list into a ranking of extensibility or developer experience.
Can active paid members move without starting again?
This is the clearest place where adjacent words can mislead. A bulk invite, customer import, product migration, email-list import, or trial offer can all be relevant to a transition while answering different questions from “Can an active paid subscription move with its billing state?”
Ask: Can active subscriptions move without member re-subscription, and are payment details, renewal dates, access history, and content included or excluded? If direct transfer is unavailable, what transition does the provider document?
The answer may be a direct transfer, a documented exclusion with an alternative, a separate import path, or no same-scope record. Those outcomes are not interchangeable, and none of them is a quality score.
What this changes in a platform decision
The table is a pre-purchase question map, not a leaderboard. Start with the operation that would be expensive to discover late: the domain you need to connect, the data you must retain, the automation you must run, or the paid transition you must protect.
Then read the matching cell and its source. If it is documented, carry the stated condition into your own checklist. If it is a different scope, do not promote the neighboring operation into an answer. If it is not recorded, send the question to the provider and save the reply with the plan, data type, and date attached.
This turns a blank into a concrete due-diligence item without pretending that silence proves a limitation. It also avoids another mistake: treating a provider’s definition of “member” or “migration” as if it were a common measurement across providers.
Scope and Methodology
- The table covers the current provider set used by the site’s pricing research and the operational questions shown in its columns.
- Every displayed claim is held in the evidence record with a source URL, checked date, and verification method. Source notes describe the scope of the cited page; they do not claim first-hand use.
- “Documented” includes a provider’s explicit statement that an option is unavailable. “Different scope” and “Not recorded” remain separate from that answer state.
- A missing or different-scope entry is not converted into a capability verdict or a recommendation.
- The article does not measure quality, ease of use, support speed, migration success, data loss, or developer experience. It records only what the reviewed official documents state and the questions they leave open.
The provider’s current terms control. Ask for the exact plan, object, and transition conditions before committing to a platform.