Imagine an Albany sole trader using a fintech app to organise account transactions and add notes about business expenses. The app is convenient, but the trader is considering another service. Before changing, they want to know whether the information can move in a form they can still understand.
This fictional scenario explores data portability, meaning the practical ability to retrieve and reuse relevant information. It does not describe an actual business or guarantee that a particular provider supports every step. The trader checks the current product documentation and seeks help for business recordkeeping obligations.
The trader separates source information from added information
The app displays transactions from an existing account, but the trader has also added categories, explanatory notes and links to receipts. Those additions may be stored differently from the transaction information. A new app receiving account data may not receive the annotations.
They make a list of what matters: dates, amounts, currency, transaction references, categories and supporting documents. They also note which information is authoritative elsewhere, such as original bank statements or supplier invoices.
The distinction changes the question to the provider. Instead of asking whether an export exists, the trader asks which of these specific elements the export includes and how they remain connected.
A sample export reveals more than a feature label
The trader requests instructions and tests an export using an appropriate small sample. They open it in a suitable local application and check whether the information is readable. A file downloading successfully is only the beginning.
They inspect several known transactions, including a refund and an internal transfer. Does the file distinguish incoming and outgoing amounts? Are currencies clear? Are long references preserved, and do dates mean the transaction date or another processing event?
- Identify the account and period covered.
- Check ordinary transactions and relevant exceptions.
- Confirm that categories and notes are included where needed.
- Find how supporting documents connect to entries.
- Record any fields absent from the export.
- Keep the provider’s explanation of unfamiliar fields.
The trader avoids editing the only original export during the test. They keep a secure source copy and use a working copy for examining the layout.
The new service is tested for interpretation, not just import
An import function may accept a file without interpreting every field correctly. The trader checks a limited sample before considering a larger transfer. They compare the imported entries with the original records and look for duplicates or missing context.
They pay particular attention to custom categories and notes. If the new service uses different labels, a mapping decision is required. It should not silently convert a carefully recorded explanation into an unrelated default category.
There is no assumption that moving information automatically satisfies tax obligations. The official business recordkeeping guide explains why transaction and supporting records matter. The trader asks their accountant what must remain available for their circumstances.
Account-data sharing and a complete app migration remain separate
The trader learns that the proposed service can receive some account information through the Consumer Data Right. They check what accounts, information and period are supported rather than assuming that the connection transfers the old app’s entire history.
The official CDR process explanation describes consent-based sharing and machine-readable transfer between providers. That framework does not mean every custom note, uploaded receipt or unrelated app setting will be part of a particular connection.
They examine data sharing permission separately from account closure and payment instructions. Moving transaction information does not necessarily move a direct debit, settle an amount owed or end a subscription.
For attachments kept separately, the trader records a consistent link between the transaction reference and file name. They open a sample receipt after copying it to confirm the file is usable. A folder containing many documents is less helpful if the connection to the relevant transaction has been lost.
The transition includes access, cost and secure storage
The trader asks whether exports remain available on the current plan and after cancellation. They check any charge for assistance and the time needed to retrieve attachments. A low subscription price can be less attractive if leaving requires substantial manual work.
Necessary files are stored securely with an appropriate backup. Downloading sensitive records onto an unmanaged shared device would create another problem, even if the export itself is complete. Access is limited to the people helping with the transition.
The trader documents the last export period and which service is being treated as current. This reduces the risk of maintaining two inconsistent working records or importing the same period repeatedly.
The decision is made with the gaps still visible
The scenario ends with a portability assessment, rather than an invented successful migration. The trader can see which information moves directly, which needs preparation and which must be retained separately. They can compare that work with the benefit of changing services.
They keep instructions for repeating the export and revisit the test when the app changes. Data remains practically portable when it can be retrieved, interpreted and connected to its context, not merely when a download button appears on the screen.