A payment dashboard is a view of business activity; it is not proof that the underlying records can be moved. Before switching providers or closing an account, test what the business can actually export and whether another person can understand it.
Define the records needed for one business task
Choose a task such as reconciling a month, answering a refund question or tracing an order to its deposit. List the necessary references, dates, amounts, transaction states and location identifiers. Ask which records are available through the ordinary export, which require support and which are subject to separate access rules.
Test a sample with linked transactions
Export a small period that includes a sale, a refund and an adjustment if those exist in the account. Check whether the export retains the relationships between them. Open it in the tool your bookkeeper or operations employee actually uses. Unexplained codes and inconsistent dates can make a technically successful export unusable.
Keep control of access and retention
Identify the employee responsible for requesting the export and storing it in an approved location. Check the provider’s agreement for post-termination access, retention and export conditions before the relationship ends. Do not assume payment credentials can be transferred like ordinary order records; ask the providers about their supported secure process.
Keep multiple locations distinguishable
For an owner with activity in Florida, New York and New Jersey, confirm that the export distinguishes locations, entities and sales channels. A common customer name is not a reliable substitute for an order identifier. This example concerns record organization and does not imply that Eric or AMS operates an office in those states.
The regional business guides provide related location-record checklists. For the full provider-transition worksheet, use A Fintech Exit Plan Needs a Usable Data Export.
Decide whether the test passed
A useful test ends when another authorized employee can complete the chosen task from the exported records and explain the remaining gaps. Save that result with the export instructions. If the test fails, resolve the missing fields or access questions while the account and support relationship are still active.
By Eric Kuvykin. Revised October 17, 2026. Examples are illustrative operating scenarios.
