Skip to main content

​
Migration from ClueControl M

If your server previously ran on the ClueControl M bot, this guide will help you transfer your shift and leave management module settings to Department Oversight. Data is transferred manually and takes about 10–15 minutes.
Shift history and statistics are not migrated automatically. Old data remains in the ClueControl M database — time tracking in the new bot will start from scratch.

​
Where Things Are Located

In ClueControl M, settings are accessed via the /config command and are restricted to Management. In Department Oversight, everything is contained in a single /configure menu — before initial configuration it is accessible to server administrators, and afterwards only to “Config Roles”. Transfer your staff roles from Basic Settings (Staff / Admin / Management) to the “Access Permissions” page — these determine who can approve leave requests and use admin commands.

​
Shifts

Page: “Shift Settings”:
The quota format is different: ClueControl M accepts 1h30m, while the new bot accepts 60m, 2h, 1d, 1mo. Recalculate your values before entering.
Shift types are recreated one-to-one: name, type log channel, duty roles, break role, nickname prefix, and access roles. The same applies to role quotas — recreate them via “Role Quotas”.

​
How to Transfer Shift Types

To make shifts work as before, you need to transfer the shift types:
  1. In ClueControl M, open /config → Shift Management page → Shift Types.
  2. Note down for each type:
    • Name (e.g., “Patrol”, “Office Duty”, “Training”)
    • Type log channel (where duty start/end logs for this specific type are sent)
    • On-duty roles (roles assigned when starting this shift type)
    • Break role (if different from the global one)
    • Nickname prefix (e.g., [PATROL] )
    • Access roles (who can select this type when starting a shift)
  3. In Department Oversight, navigate to /configure → Shift Settings → Shift Types → “Create Type”.
  4. Fill in the fields strictly according to the recorded data:
    • Name — identical
    • Log channel — select the same channel (or create a new one if restructuring)
    • On-duty roles — add the same roles
    • Break role — specify if configured previously
    • Nickname prefix — copy character for character (note: in ClueControl M the prefix was placed before the nickname, same as in the new bot)
    • Access roles — select the same roles that were allowed to use this type
  5. Repeat for each shift type.
  6. After creating all types, verify: start a test shift using /shift manage → select the type → ensure proper roles are granted, prefix is applied, and logs are sent to the correct channel.
If ClueControl M had many shift types (5+), create them in bulk first, then test each one — this is much faster than creating and testing them one by one.
Important: In the new bot, shift type access roles require the member to have at least one of the specified roles for the type to appear in their menu. Verify role assignments accordingly.

​
Leaves and Reduced Activity

Page: “Leave Settings”: What has changed compared to ClueControl M:
  • Separate toggles — accepting leave and reduced activity requests is enabled independently rather than with a single switch;
  • Dedicated RA channel — reduced activity requests no longer drop into the general leave channel;
  • Fixed durations — employees select from a list: 1, 3, 7, 14, 21, 30, 60, or 90 days (instead of freeform s/m/h/d);
  • Rejection reason is mandatory — it is sent directly to the employee’s DMs;
  • RA credit — during reduced activity, 50% of the standard time quota applies;
  • Approvals are available to management-level roles configured in “Access Permissions” or Discord administrators.

​
Command Mapping

​
Disabling Modules in ClueControl M

After setting up Department Oversight, disable the same modules in the old bot so they do not run concurrently. In ClueControl M, open /config and switch the selectors to Disabled on two pages:
  • Shift Management page — selector “Shift Management” → Disabled;
  • LOA Requests page — selector “LOA Requests” → Disabled.
In ClueControl M, the single “LOA Requests” toggle manages both leaves and reduced activity — no separate switch is needed for RA.
While a module is disabled, shift and request commands respond with a “Not Enabled” message — staff will stop using them and fully switch to the new bot.

​
Migration Checklist

  1. Grant access to your leadership team: “Access Permissions” → “Config Roles” and management roles.
  2. Enable shifts, specify the log channel and on-duty role.
  3. In “Additional Options”, set the break role, nickname prefix, staff limit, and shift quota (in the new format).
  4. Recreate shift types and role quotas.
  5. Configure leaves: enable request intake, specify the channel and leave roles.
  6. Configure reduced activity: dedicated channel and roles.
  7. Verify that staff can start shifts via /shift manage and that leave requests arrive in the review channel.
  8. Disable modules in ClueControl M to prevent them from running across both bots simultaneously.