Scout SuiteHow-to guide
Syncing from OSM
This is a repeatable import, not a one-click move. While sync is enabled, mapped fields in Scout Suite can be overwritten on the next run — that's the deal you tick before it starts.
Connect OSM for sync
Under Settings → OSM sync, connect with the extra permissions the import needs — signing in with OSM on its own isn't always enough. You're looking for OSM sync access ready and Sync enabled. Authorize OSM sync (or Connect OSM for sync) if the page says permission is missing.
Pick sections, terms and a scope
Load OSM sections, then Sections and terms (current terms are selected by default). Sync scope starts with Sections, Terms, Members and Contacts — Sections and Terms stay on. You can add events, programme, attendance, badges, patrols, payments and Gift Aid, and more; some of those have limits or warnings on the page (census is called out as special-category data; membership history and file attachments cap how many members per run).
Preflight, then run
Tick that you understand OSM is the source of truth while sync is enabled. Run OSM preflight is a dry run — it stops on the first failed OSM response and writes nothing. Then Run sync. Previous runs shows counts and row errors; Run again reuses the same settings.
This is not the same as the high-level Migrate from OSM page — that's planning copy. This page is the actual import.
Direct Debit mandates are not brought across. OSM section login accounts (who can log in to OSM) cannot be imported — OSM’s API refuses that even for group admins. Event resource files are counted, not downloaded.
Gift Aid declarations imported here don't arrive linked to a parent or contact, so they won't pack into a claim until you record a proper declaration — see Claiming Gift Aid.
Waiting list is not in the OSM API. Use CSV fallback on the same settings page: export from OSM, then upload. First name, last name and parent email are required.
Setup
More in this topic
Districts, WordPress, OSM, SSO, the API, privacy mode, and the assistant.