Must know
- The import is four stages — probe, plan, apply, verify — and only apply writes. The plan is a document your club reads before anything runs; verify recomputes your standings from the imported data and compares them to CCM’s before the migration is called done.
- Running apply twice creates nothing twice. It is safe to resume.
- Scale, measured on a real club: 4,254 members, 21,582 profile answers, 1,820 money rows, 36 programs, 569 teams and 13,626 facility-calendar rows in one apply.
People
- Members — every Community Builder account becomes a member with a login by email (no password; see How do members log in after the move?). A person who already exists on the platform from another club is adopted, never duplicated or rewritten.
- Your Community Builder fields — each of the club’s own CB fields arrives as a club field under Settings → Profile Fields, with its tab, its real type (drop-down, multi-select, yes/no, date, text area, email, web address or text) and its Required, Profile, Edit, Searchable and Published flags. The import switches on the Custom Information feature for a club that has such fields. Members see the fields on My Information in the tab CB showed them in. See Where did Community Builder Field Management go?.
- Profile answers — the Curling Club Info fields and every other CB answer, as each member’s values in those fields.
- Association member number — CB’s
cb_gnccid(GNCC) orcb_uscaid(USCA) column becomes the member’s Federation Membership number, under USA Curling, exactly as stored. If a club has both columns,cb_gnccidis used and the other stays a club field; the plan warns about that, and about any number that does not look like a USA Curling number. The number fills GNCC - ID in the GNCC Format Report. CCM’s built-in club number and region are not carried over: enter yours under Settings → Club Settings → Association exports (see How do I export the GNCC and USCA member files?). - The club’s Step 1 field list — which of CCM’s 18 signup fields your club used and in what order, written into your Registration Form. CCM had no “Additional questions” screen, so an imported club’s wizard has none either; its custom questions are still asked at checkout.
- How empty standings cells print — CCM v3 printed a standings cell with nothing recorded as 0, CCM v5 left it blank. The import sets the club’s Show 0 in empty standings cells switch to match, so members see what they saw before.
- Community Builder field titles in two languages — a title written English;;;Français arrives as the field’s English title and its French title, instead of the whole string. French-language members see the French title (and the French half of a two-language answer choice). Descriptions written the same way are split too.
- Payment history — the five CB payment slots and the online signup total, from whichever gateway your club used (GlobalPayments, Square, Authorize.net, Stripe, Clover or Moneris), as payments on an imported invoice with the gateway’s reference. Recorded, never re-chargeable. Unpaid signup totals import as owing.
- The club’s words — Subbing/Sparing, Round/Draw/Flight, Division/Pool.
- The default view — classic, for your staff on the dashboard. Members always get the new pages.
- Signup at Confirm — Book registrations at Confirm is switched on with a 7-day hold, so a member’s Confirm records the signup before payment, as CCM’s did. Unlike CCM, an unpaid entry is released when the days run out. See How do I let members book at Confirm and pay later?.
Leagues
- Leagues, divisions, rounds, teams, games and points, including leagues split across CCM’s cloned per-session tables, which arrive as one league with several sessions.
- Each league’s place on signup. A league CCM listed on its signup (published and Show On Sign-up) and had not marked full arrives open for registration. A league CCM marked full arrives closed and shows as FILLED in the wizard, as CCM showed it. Every other league arrives closed. Registration therefore goes live the moment the domain moves — see What happens on cutover day?.
- Who last edited each result — the Edited By name on CCM’s game list, where your CCM version recorded it. CCM kept no edit time, so none is shown.
- Byes against “Nobody” — the “vs Nobody” games CCM’s generator saved arrive as the same sheetless bye on their league night, instead of disappearing.
- Points rules per round × division, and the game points CCM stored — remember that CCM’s “score” columns held league points awarded, not curling scores.
- Sub lists per league, lockers (from the four CB locker fields), and history seasons from CCM’s history table.
- Facility-calendar rows as bookings, at the hour the club booked them. CCM stored these times in UTC; the import converts each one to your club’s time zone, so a booking keeps its local time across daylight-saving changes. Before anything is written, the plan checks that reading against your league games and stops for a decision if a site stored local times instead. CCM’s own calendar copies of league games are left out (see What the import does not bring), so league draws are not booked twice. Each CCM resource is also listed on the Resources screen, under one facility named after your club, with its published state, its access (CCM’s Public stays Public; Registered and Special become Private) and CCM’s order. Each imported venue is linked to its resource, so a resource that was hidden from guests in CCM still hides its bookings from the public. See Who can see a venue’s bookings?.
Volunteers
- Volunteer roles and sub-roles, with their descriptions (formatting kept) and CCM’s order.
- Sign-ups. A CCM volunteer row that names a sub-role becomes a sign-up on that shift, with its comment, so each imported shift’s filled count matches CCM’s. A row with no sub-role stays an interest in the role.
- Time-tracker hours. CCM stored logged time in minutes; it arrives converted to hours, with the sub-role the member logged it against as the entry’s Task.