You can always take your data and leave

Workspace owners can export the whole workspace from Settings → Workspace → Export data in the app, or by calling GET /api/v1/workspaces/{id}/export with an owner token. The export is generated on request and downloaded directly; it is not stored on our side.

Everything in Falrow is also readable through the documented REST API and the MCP server, so you can build a continuous sync to another system if you prefer.

All data you and your Users and Agents put into the workspace, and the data generated from it about your work, is exportable:

• workspace settings, projects, applications, stages, labels, ticket types, templates and workflow rules;
• tickets with their full history, comments, documents, attachments stored in Falrow, cycles, milestones and saved views;
• customers, CRM contacts and meeting notes;
• members, their roles and capacity;
• operations boards, budgets, reminders and webhook configuration (without secrets);
• the workspace activity log.

Not exported, because it would expose credentials or our trade secrets rather than your data: encrypted integration secrets and API keys, token and password hashes, our system prompts, and internal job queue state. You can re-create integrations at your new provider with fresh credentials.

These are open, documented formats. We do not know of any technical restriction that would prevent a destination provider from importing them, beyond mapping Falrow's record kinds to its own.

• Notice. Tell us in the app or at bas@falrow.com that you want to switch to another provider, move to your own infrastructure, or have your data erased. The maximum notice period is two months; you can choose a shorter one.
• Transition. After the notice period, a transition period of up to 30 calendar days starts. During it the Service keeps running at the same level, we give reasonable help to you and to your new provider, and we tell you about any known risk to continuity. You may extend the transition period once, for as long as you consider appropriate.
• Retrieval. After the transition, you have at least 30 more days to retrieve your data.
• End and erasure. When the switch is complete we confirm that the agreement has ended, and then erase your exportable data and workspace from production within 30 days and from backups on their rolling cycle of no more than 35 days.

If the 30-day transition is technically unfeasible in your case, we will tell you within 14 working days of your request, explain why, and propose an alternative of no more than seven months.

There are no switching charges and no data egress charges. Exports, API access and help with switching are free. If you have prepaid a fixed term, the Order says whether unused fees are refunded; an early termination fee, if any, is set out in the Order before you sign and is never a charge for switching itself.

Workspace data is stored in Frankfurt, Germany, and processed by the application in the Netherlands. The Subprocessors page lists every provider and location, and the Legal Notices page describes the measures we take against unlawful government access, as Article 28 of the Data Act requires.