Partners sourced from the legacy configuration. Select one to work on; this feeds the panels below. Migration status is shown in the live side-by-side for the selected partner.

No partners found.

2. Properties

Select a partner above to list its properties.

3. Historical booking sync

Every invoke emails a CSV report to the recipient below — including the dry-run mode. For a clean run the partner config must be migrated first; a non-zero config-error count in the returned summary is expected, not a failure.

Select a partner above to compose an event.

4. Migrate

Transforms the selected partner's legacy records (partner config and property links) to the current schemas. A dry-run validates every record without writing; turning the toggle off writes each valid record through the config gateway. If no properties are ticked, all of the partner's properties are migrated. Booking links are migrated separately below.

lastChecked is intentionally not migrated or managed by this tool — it is left untouched in both stores.

Select a partner above to migrate.

5. Migrate bookings

Migrates ALL booking links across the whole partition, independent of the partner selected above — booking-link records carry no partner or property field, so they cannot be scoped to a selection. A dry-run validates every record without writing; turning the toggle off writes each valid record through the config gateway. Records with no usable sort key are skipped and reported, never written.