Migration Notes

Template Strategy Evolution

SafeCall deployments may differ depending on release history:

• older setups commonly used separate template strategy for different beacon device classes (for example watches vs panic buttons)
• current CLI auto-configuration in this repository provisions:
  • SafeCall Gateway
  • SafeCall SOS Button
  • SafeCall Watch

If your environment uses a unified beacon/watch template strategy, keep zabbix verify focused on object presence and discovery correctness rather than template naming alone.

Recommended Migration Workflow

1. Export existing Zabbix templates and discovery rules (backup).
2. Run ./util.sh integrations zabbix setup --dry-run and compare expected objects.
3. Decide whether to keep legacy names or re-align to current generated names.
4. Run ./util.sh integrations zabbix setup ... to reconcile missing objects.
5. Run ./util.sh integrations zabbix verify ... to confirm final state.

Mixed Environments

During phased migrations, it is valid to have:

• legacy templates still linked to existing hosts
• new discovery rules producing hosts linked to current templates

Use host groups and naming conventions to avoid ambiguity while transition completes.