Flixcheck is built to collect data, documents and signatures from end customers, so much of what sits in an account is a form rather than a contract, and that sets the scope of the move before anything is exported. What follows is specific to leaving Flixcheck: what to take, how it comes out, and what to watch on the commercial side.
Sort the contracts out of the Checks.
Meter readings, claims reports and address changes are forms, and they stay forms, in Flixcheck or elsewhere. Go through your Check templates and mark the ones that are really agreements with a term, a notice period or a renewal date. Only those belong in fynk. They can be a smaller share than the monthly Check count suggests, because that count includes every form a recipient opened and started.
Plan the Check export before you give notice.
Flixcheck’s pricing page lists a Check export with structured data as PDF, CSV or through the API. The API route only helps accounts with API access, which the current pricing page places on Enterprise. A tool that exports the whole archive in one go is not documented, so ask Flixcheck early how a complete export works for your account, and budget time for it. Keep both formats: fynk reads the PDFs on import, and the CSV files keep the answers the forms collected in a table.
Do not rely on the ten-year retention.
Flixcheck’s help centre says documents are kept for ten years by default. That describes the running account, not what happens after you leave, so ask in writing what becomes of stored Checks once the contract ends, and export before that date. Watch the term as well: annual billing carries a twelve-month minimum and renews automatically, monthly billing a one-month minimum. Note the renewal date, give notice in time, and pick a day from which new contracts start in fynk while open Checks finish in Flixcheck.
Who notices, and what there is to rebuild.
The current pricing page includes no API access on Starter, Professional or Business, so on those plans there is usually no API connection to rebuild. If you are on Enterprise, list what the API feeds today and plan for fynk Business, where the API and webhooks start. The biggest change is for the people who handle contracts: instead of a form the counterparty fills in, a contract in fynk is drafted from a template, negotiated with tracked changes, approved internally and then signed, with SES, AES or QES on every plan. End customers who only fill in forms notice nothing as long as those forms stay in Flixcheck.
Where leaving Flixcheck genuinely does not work.
If your work is mostly sending forms to many end customers by SMS or WhatsApp, reading ID documents and collecting simple or advanced signatures, Flixcheck is built for exactly that. If hosting only in Germany is a hard requirement, Flixcheck meets it more narrowly than fynk’s hosting in the European Economic Area. Staying is the right answer then, or a split: Flixcheck for the forms, a contract system for the contracts. Saying so here costs both sides less than finding it out in the third month.