Nobody reads the export clause until they need it. By then the vendor is being acquired, wound down, or simply sunsetting the product line your portfolio happens to sit in, and the question stops being hypothetical: what do you actually walk away with, and on what timeline.
The retention duty is yours, not the vendor's
German tax law gives accounting-relevant records a ten-year retention requirement under GoBD, and that duty sits with the property owner, not with whatever software happened to generate the records. A vendor closing its doors does not close your obligation to produce those records to the Finanzamt on request. If the only copy lived inside a system you can no longer log into, that is a problem you own, not one you can point a auditor toward.
What a typical export window actually promises
Most SaaS contracts include a data export commitment, and most of them are looser than they sound: export available for 30 to 90 days after termination, in "a standard format," a phrase vague enough to mean anything from a clean relational export to an awkward CSV dump that takes weeks to reconcile back into something usable. That is the commitment in an ordinary, planned offboarding. An insolvency changes the arithmetic: an administrator's job is an orderly, cost-minimising wind-down, not customer support, and the same export promise can become aspirational the moment keeping servers running stops being the cheapest option.
Why the contract term matters before any of this is tested
A long minimum term compounds the risk rather than causing it. onOffice enterprise runs on a 24-month minimum contract, as laid out in REPM vs onOffice, which means that if you start to have doubts about a vendor's direction, you may simply not be able to leave before the doubts are confirmed. REPM is billed per environment and cancellable at any renewal with no 24-month lock. That does not prevent a vendor problem from happening. It means you are never contractually stuck waiting one out.
What is actually different about a Dataverse-native record
REPM runs inside your own Microsoft Dataverse tenant, not a database inside REPM's own infrastructure shared across customers. The practical difference: if Woods Business Solutions stopped operating tomorrow, the tables in your tenant do not disappear with it, because they were never REPM's tables to begin with, they are yours, licensed through Microsoft. Power BI, Excel, and the Dataverse Web API all still read against that environment independent of any one ISV's continued existence. What would stop is maintenance of the application layer itself, the forms, the model-driven app, the flows and plugins that make the data pleasant to work with day to day. The records underneath stay queryable. That is a genuinely different exposure than a typical multi-tenant SaaS product, and it is worth being precise about the distinction rather than promising more than a structural fact supports.
See where your data actually lives. Start a free REPM Lite trial at app.repm.cloud and check the environment settings for yourself.
FAQ
Does my GoBD retention duty end if my software vendor closes?
No. The ten-year retention requirement under GoBD applies to the property owner, not the software vendor. If a vendor shuts down and the records are unrecoverable, the retention obligation still applies to you.
What should I actually check in a vendor contract before signing?
Two things, separately: the data export format and window on termination, and the minimum contract term. A short export window is a manageable risk if you can leave whenever you want. A long lock-in makes any later vendor concern much harder to act on.
What happens to REPM data specifically if Woods Business Solutions stopped operating?
The Dataverse tables sit in your own Microsoft tenant, licensed through Microsoft rather than hosted on REPM's own infrastructure, so they remain queryable through standard Power Platform tools. What would stop is active maintenance of the REPM application itself, the forms, flows and business logic layered on top of that data.
Is Dataverse itself something I could lose access to?
Dataverse access runs on your own Microsoft Power Platform licensing, independent of any single ISV. Losing an application vendor does not affect your underlying Microsoft tenant or licensing relationship.