Migrating from another freeze tool

Moving from an older freeze tool is two steps. There is no importer — a one-click import of your existing repository list and schedules is on the roadmap and is not built, so this page describes what works today.

1. Install Fwozen alongside your current tool and enable the same repositories. Nothing breaks while both are installed: two required checks simply both have to pass. Recreate your schedules in the Fwozen schedule builder, which shows the next five occurrences in the schedule’s timezone and in yours before you save.
2. Change one base URL. Fwozen serves a compatibility namespace that accepts the request shapes and returns the response field names the previous generation of tools used, so your automation itself does not change.

# before
BASE_URL=https://your-old-freeze-tool.example/api

# after
BASE_URL=https://api.fwozen.com/api/compat/v1

Everything after the base URL — paths, query parameters, request bodies and response field names — stays exactly as it was. Once the base URL is switched, remove the old app’s required check from your branch rules and uninstall it.

Paying for a freeze tool today? Show us the invoice and we will match the price for twelve months. This page is expanding with a field-by-field mapping of the compatibility layer.