An export button can produce a file without producing a usable archive. The file may contain current balances but omit the transactions that explain them, or it may list attachment names without including the attachments. Before cancelling an old rental software subscription, test whether the records you need can actually be found, opened and understood outside the original account.
This New York edition guide describes an operational exit test using fictional records. It does not prescribe retention periods, determine legal obligations or report a completed test of any software product. Your actual records may require professional advice about retention and security. The immediate question is whether the proposed export preserves the information and relationships your authorized reviewers need.
Define the record package before pressing export
List the categories you expect to retain: property and unit identifiers, resident records, transactions, work requests, approvals, communications and attachments as applicable. For each category, state why it is needed and who should be allowed to view it. A broad request for everything can produce a large archive that nobody has checked carefully.
Separate the business record from the application’s presentation. A dashboard total may be useful, but a future reviewer may also need the underlying entries and their dates. Conversely, a collection of raw entries may be difficult to interpret without field definitions. Decide what combination of structured files, documents and explanatory notes would make the package usable.
Ask the provider what export options exist for your actual account and plan. Obtain current answers about formats, attachment access, timing and what happens after cancellation. Treat a support statement as information to verify, not as a substitute for opening the exported files yourself.
Choose a small known test set
Create a fictional exercise containing a few records with relationships that are easy to check. Include two properties, several units, a payment, a correction, a work request and an attachment. Use names that cannot be confused with real residents, and avoid uploading sensitive material merely to make the demonstration realistic.
Include a record that changes over time. An amended work request or corrected transaction helps reveal whether the export preserves a useful history or only the latest display. Record the expected behavior in advance so the test does not become a search for whatever the system happens to provide.
Keep a reference sheet containing the intended counts and relationships. This is your independent expected result. If the only source for the expected total is the exported file itself, the test cannot reveal an omission that affects both the detail and the total in the same way.
| Category | Expected evidence | Test action | Result |
|---|---|---|---|
| Identifiers | Stable property and unit references | Trace records across files | Pass, gap or unresolved |
| Transactions | Known counts and selected totals | Recalculate independently | Record differences |
| Attachments | Readable files connected to records | Open without old account | Note missing links |
| History | Required changes and timestamps | Review fictional correction | Describe available detail |
| Access | Authorized reviewer can retrieve | Test controlled archive copy | Confirm permissions |
Inspect structure before reconciling numbers
Open the files using the tools you expect to have after cancellation. Check the column headings, date formats, character handling and identifiers. A date that can be interpreted in two different ways needs an explicit format note. A unit identifier converted into a number may lose meaningful leading characters.
Check whether one row represents a transaction, a line within a transaction or a summary. Counting rows without understanding their meaning can produce a false discrepancy. Ask the provider for field definitions where necessary and preserve the explanation with the archive rather than relying on someone remembering it later.
Look for fields that contain links into the old application. A link may be useful while the account remains active but fail afterward. Determine whether the actual document is included in the export or requires a separate download. Do not assume that a filename displayed in a table proves that its contents were preserved.
Reconcile a hypothetical transaction set
Suppose a fictional test contains three selected receipts of $500, $700 and $300. Their total is $1,500. It also contains a separately recorded reversal of $100, so the intended selected net is $1,400. These invented figures are a test fixture, not a statement about New York rents or accounting treatment.
If the export shows the three receipts but omits the reversal, the gross total can look correct while the net is wrong. If it shows only the $1,400 net without the component entries, the total can be correct while the explanatory history is missing. Your acceptance criteria need both the required amounts and the required level of detail.
Now assign the $500 and $300 receipts to Property A and the $700 receipt and $100 reversal to Property B. The selected property totals should be $800 and $600. A grand total of $1,400 does not prove that the property assignments survived. Reconcile by property as well as across the complete test set.
Finally, include four fictional attachments, with two attached to one work request and one attached to each of two other records. Confirm that all four open and that their relationships remain identifiable. Four files in a folder are insufficient if nobody can tell which request originally contained the pair.
Test retrieval without relying on the old interface
Give an authorized reviewer a controlled copy of the test archive and a specific question. Ask them to find the document supporting one transaction or identify the approval associated with a repair. They should be able to answer using the archive and its notes, without asking the person who performed the export to reconstruct the history.
Record how the reviewer found the answer and where they became stuck. A simple index or field glossary may solve a retrieval problem without changing software. A missing attachment or omitted category requires a different remedy. Distinguish usability improvements from missing evidence so the final plan addresses the actual gap.
Repeat the test for a record with a correction or a changed name. Stable identifiers should help connect the history even when the visible label differs. If the export lacks such identifiers, document a reliable mapping before cancellation rather than assuming future reviewers will recognize every name variation.
Protect the archive during transfer and storage
Limit the exported material to authorized people and approved storage locations. Exporting records can create additional copies containing sensitive information, even when the purpose is legitimate. The FTC guide to protecting personal information provides general background on knowing what information you hold, limiting what you retain and controlling access.
Do not email an entire archive simply because a reviewer needs one document. Create a suitable controlled package for the particular task. Check whether a temporary sharing link remains active after the review, and assign responsibility for removing unneeded working copies in accordance with the applicable retention and security requirements.
Keep a manifest identifying the export date, account, categories, file names and known limitations. Store credentials separately from the archive. An archive that includes an explanation of access requirements can remain useful without embedding passwords in the same package as the records they protect.
Schedule cancellation only after the acceptance decision
Make a written list of any unresolved gaps and the person responsible for each. A cancellation date should not silently become a deadline for pretending those gaps do not matter. If an essential category is missing, obtain a remedy or an informed decision from the appropriate owner before relying on the archive.
Check whether records can change between the test export and the final export. Define a final cutoff, a method for capturing later activity and a reconciliation between the tested package and the final package. Otherwise a successful test can create false confidence in a final archive that omits the last days of activity.
Preserve the provider’s cancellation confirmation and relevant account communications with the administrative record. Do not assume that cancellation, data deletion and loss of access occur at the same time or under the same conditions. Confirm the actual terms for the service you use.
Document the meaning of empty fields
Review a few deliberately empty fields in the test export. An empty value might mean the information was never entered, the category does not apply, the field was excluded from the export or the user lacked access to it. Those meanings should not be collapsed into one assumption when another reviewer uses the archive.
Where the provider can explain the behavior, preserve that explanation in the field glossary. Where it remains uncertain, record the limitation and test a known populated value before accepting the export. This small check is especially useful for optional notes and attachments, because a file can open normally while concealing that an entire class of information was omitted.
Evaluate replacement software using the same evidence
Use the software scorecard to record demonstrated export capabilities, limitations and support responses. Testing the exit process before adopting another system is easier than discovering the constraints during the next transition. No product should receive a passing score based solely on an export label in a feature list.
Affiliate disclosure: Homzora may earn a commission through the following links. Buildium and Rentec Direct are optional candidates for your own evaluation. This article makes no claim that either product passes the fictional export exercise or offers a particular feature in your account.
Have the accepting reviewer record the archive version they inspected, so the final decision cannot accidentally refer to a different export made on another date.
Return to the New York edition for related operational resources. The result of this process should be a tested archive and an explicit acceptance decision, with known limitations preserved for the people who will depend on those records later.