This article explains how the Wonde data synchronisation works, including the automatic sync schedule, the two sync phases, member matching, and how to run or pause syncs. It is intended for d6 support staff and school administrators.

Mission Control > Customer Success > Integrations > Wonde > Sync Settings

How often does the Wonde sync run?

The sync runs automatically three times per day at 04:00, 10:00, and 16:00 UTC. This means there is a maximum 6 to 10 hour delay between when data changes in the school's Management System and when it appears in d6. For urgent updates, a manual sync can be triggered via Mission Control.

What are the two phases of the sync?

The Wonde sync runs in two distinct phases:

• Phase 1 — Data sync (Wonde API to d6 database): Fetches the latest data from Wonde and stores it locally. This includes students, parents/contacts, employees, groups (year groups, houses, tutor groups), and classes (subject classes) along with their relationships.

• Phase 2 — Internal sync (d6 database to groups): Transforms the Wonde data into d6 members and groups using assignment sets. This phase runs in order: first removing members no longer in Wonde, then creating or updating member records, and finally linking members to groups and establishing parent-child relationships.

How does member matching work?

During Phase 2, the system matches incoming Wonde data against existing d6 members using email or phone number. If a match is found, the existing member record is updated. If no match is found, a new member is created. Only members originally created by the Wonde integration are affected — manually created members are never touched by the sync, even if they share the same name or email.

What happens when someone is removed from Wonde?

If a person no longer appears in the Wonde data, they are removed from d6 on the next sync. This only affects members originally created by the Wonde integration. Members who were manually added to d6 are never deleted or modified by the sync process.

How do I run a manual sync or pause automatic syncs?

To run a manual sync, kindly contact your Customer Success Consultant on support@d6ed.co.za.

Your agent  with then "Run Sync" for your community. You can choose a full sync (both phases), data only (Phase 1), or internal only (Phase 2). To pause automatic syncs — for example during school holidays — toggle the "Pause Sync" option. Manual syncs are still possible when paused.

Expected sync durations: small schools (under 500 students) take 1 to 3 minutes, medium schools (500 to 1,500 students) take 3 to 7 minutes, and large schools (over 1,500 students) take 7 to 15 minutes.

Frequently asked questions

Why is there a delay between updating data in the Management system and seeing it in d6?

The sync runs three times per day, not in real time. Changes made in the Management System will appear in d6 after the next scheduled sync, which could be up to 6 to 10 hours later. A manual sync can be triggered for urgent updates.

Will manually created members be affected by the Wonde sync?

No. The sync only affects members originally created by the Wonde integration. Manually created members and manually added group memberships are completely separate and never modified or deleted by syncs.

Can I run two syncs at the same time for the same community?

No. Only one sync can run at a time per community. If a sync is requested while another is in progress, you must wait for the current one to complete.

What is the difference between a full sync, data only, and internal only?

A full sync runs both phases: fetching data from Wonde and then updating d6 groups. Data only runs Phase 1 (fetching from Wonde). Internal only runs Phase 2 (updating groups from the local database). A full sync is recommended in most cases.