Exit, Data Portability & Offboarding
This document answers a single question that procurement and IT reviewers commonly ask: "If we decide to leave, can we get our data out, and what happens to it?" It describes where Boxcurve Unity holds your data, the portability features the application provides, how you remove the product, and where responsibility sits. Where a point depends on commercial terms rather than the application itself, it is marked as defined in your agreement with Boxcurve.
Summary
- All of the application's working data lives in your own Microsoft Dataverse environment, inside your own Microsoft 365 tenant. It never leaves your tenant to be stored by Boxcurve.
- There is no separate Boxcurve-held copy of your application data. The only information Boxcurve receives is a licensing check (see What Boxcurve receives).
- Boxcurve Unity includes a built-in task export to CSV, delivered to OneDrive, as a portability feature.
- A full extraction of all of the application's Dataverse tables is available to you at any time through your own Microsoft platform tooling, independently of Boxcurve.
- Because the licence check fails open, a lapsed or cancelled Boxcurve subscription does not lock you out of your own data.
Where your data lives
Boxcurve Unity is a Power Platform application backed by Microsoft Dataverse. Every record the application creates and maintains, projects, tasks, the Accountability Map and its assignments, the stakeholder register, comments, change history, settings and logs, is stored in the Dataverse environment within your Microsoft 365 tenant.
This has a direct consequence for exit planning: on exit, your data does not need to be returned to you, because it was never held anywhere else. It remains under your control in your tenant, governed by your tenant's own administration, retention and backup arrangements. Removing the product (covered below) changes what is in your environment; it does not transfer custody of anything to Boxcurve, because Boxcurve never had custody.
Administration of the Dataverse environment itself, backups, capacity, environment-level retention, is a function of the Microsoft Power Platform, not of Boxcurve Unity. See Microsoft's guidance: Power Platform administration.
Getting your data out
You have two complementary routes to extract data, and you can use either or both without involving Boxcurve.
1. Built-in task export to CSV
Boxcurve Unity provides a task export feature. From within the application, a project's task data can be exported to CSV and delivered to OneDrive. This is a genuine, in-product portability feature for task data.
It is, by design, a task-level export rather than a complete export of every table the application holds. Use it when you need the task content of a project in a portable, spreadsheet-friendly format; for everything the application stores, use the full extraction route below.
2. Full extraction of all application tables
Because the application's data lives entirely in your own Dataverse environment, you can extract all of its tables, projects, tasks, assignments, stakeholders, comments, change history, settings and logs, using your own Microsoft platform tooling, at any time, with no dependency on Boxcurve and no Boxcurve involvement required.
The mechanisms for doing this (for example exporting Dataverse tables, or using the platform's data export and integration capabilities) are provided by Microsoft, not by Boxcurve Unity. For the authoritative, current procedure, follow Microsoft's documentation rather than steps reproduced here:
- Exporting and managing Dataverse data: Dataverse data management.
This route gives you a complete copy of the application's data in a form you control, independently of the application and of your Boxcurve subscription status.
What Boxcurve receives
To be explicit about what leaves your tenant in normal operation: the application performs a licensing check against a Boxcurve-operated licensing service. That check conveys your tenant identifier and licence / notification metadata (for example the plan in effect and update notifications). It does not transmit your projects, tasks, stakeholder records, comments or any of the application's working data to Boxcurve.
Consequently there is no Boxcurve-held repository of your application data to retrieve, reconcile or have deleted on exit. The integrations the application can connect to (for example Microsoft Planner, Azure DevOps, or an optional monday.com connection) operate through connections that you configure and own; data shared with those services is governed by your configuration of them, not by Boxcurve.
No lock-in: the licence check fails open
The licensing check is fail-open. If the licensing service cannot be reached, or if your Boxcurve subscription has lapsed or been cancelled, the application does not bar you from your environment or your data. The licence result drives in-application messaging (such as update notifications); it is not an access gate that, on failure, would lock you out of the data sitting in your own Dataverse environment.
The practical effect for an exit reviewer: ending your relationship with Boxcurve does not strand your data. Your records remain available to you in your tenant regardless of subscription state, and the extraction routes above continue to work because they are properties of your own Microsoft environment, not of Boxcurve's service.
Removing the product
Boxcurve Unity is delivered as a managed solution. You remove the product by uninstalling that managed solution from your Dataverse environment, using your own platform tooling, the same way any managed solution is removed.
Uninstalling a managed solution removes the components the solution introduced, which can include the application's tables and the data held in them. The precise behaviour of a managed-solution uninstall, what is removed, what may be retained, and how dependencies are handled, is determined by the Microsoft Power Platform, not by Boxcurve Unity. Before uninstalling, extract any data you wish to keep (see Getting your data out), because uninstalling can remove the application's data along with its tables.
For the authoritative behaviour and procedure, follow Microsoft's guidance:
- Removing solutions: Manage solutions in Power Platform.
Recommended exit sequence
- Run the built-in task export for any projects whose task content you want in CSV.
- Perform a full extraction of the application's Dataverse tables using your own platform tooling.
- Confirm your extracts are complete and stored where you need them.
- Uninstall the managed solution.
Boxcurve-provided offboarding assistance
Any assistance Boxcurve provides during offboarding, for example transition support, migration help, a data-deletion certification, or defined timelines for any of these, is a commercial matter defined in your agreement with Boxcurve, not a function of the application. The application itself imposes no such commitments and provides no such artefacts. Refer to your agreement with Boxcurve for the assistance, certifications and timelines that apply to you.
Because Boxcurve holds no copy of your application data, a request for Boxcurve to delete your application data is not applicable to that data, it resides in your tenant and is disposed of by you when you extract and uninstall as above. Treatment of the licensing metadata that Boxcurve does receive is, likewise, defined in your agreement with Boxcurve.
Responsibilities at a glance
| Area | Boxcurve Unity provides | Your responsibility |
|---|---|---|
| Storage of application data | Stores all data in your own Dataverse environment | Administer, back up and retain that environment |
| Task export | Built-in task export to CSV (to OneDrive) | Run the export; store the output |
| Full data extraction | Data resides in your tenant, extractable by you | Perform the extraction using your platform tooling |
| Removing the product | Delivered as an uninstallable managed solution | Extract data first, then uninstall |
| Continued access on lapse | Licence check fails open, no lock-out | None |
| Offboarding assistance / certifications / timelines | , (defined in your agreement) | Refer to your agreement with Boxcurve |