Before ending a restaurant POS contract, request the records you need in usable files, check representative samples against the old system, and get access deadlines in writing. Assign one person to each record group and another to confirm where the files will be stored. Do this before giving up access to the account.
A download is not necessarily a usable handoff. A folder of reports may show sales totals without the order-level detail you need. A spreadsheet may contain employee IDs without a key explaining them. Your request should specify the records, date ranges, formats and definitions needed to understand the files after the old account closes.
Inventory records and assign owners
Start with the decisions and questions your team may need to answer later. An owner may want to review historical sales. A manager may need menu details. The person responsible for payroll may need time records. Your accountant may need settlement reports. Ask each person what they use now and what they cannot reconstruct from another source.
The table below is a starting inventory. The suggested owners are responsible for requesting and checking their records; they do not all need access to every file. Add other systems if ordering, reservations or payments are managed separately from the POS.
| Record group | Request | Suggested owner |
|---|---|---|
| Orders and sales | Order detail, refunds, voids, discounts and sales reports, with dates and order IDs | Owner or general manager |
| Menu | Items, categories, prices, modifiers, availability and item identifiers | Menu manager |
| Employees | Employee identifiers, roles, time records and available adjustment history | Payroll lead |
| Payments and settlements | Transaction detail, settlement reports, fees, refunds and deposit references | Bookkeeper or accountant |
Ask whether customer profiles, gift card balances, loyalty records, house accounts or reservations are relevant to your operation and exportable. For each group, identify the system that holds the authoritative record. A payment processor may hold settlement information separately from the POS; an ordering service may hold customer details separately from order reports.
Do not assume an export contains sensitive payment credentials or that you should store them. Ask the provider what the file includes and how it should be handled. Limit access to employee and customer records, use secure storage, and agree who can retrieve the archive. Ask qualified advisers about any retention or contract questions that apply to your business.
Request formats, dates and definitions
Send the outgoing provider a written list rather than asking for “all our data.” Specify the first and last dates needed, the locations covered, the report time zone and whether the end date includes the full business day. If your restaurant serves past midnight, ask how the system assigns those orders to a business date.
Request machine-readable files such as CSV where available, plus readable reports when they provide useful context. Ask for a data dictionary explaining each column, status and code. A PDF can be helpful for a human review, but it may be difficult to sort or reconcile. Ask whether large exports are split into multiple files and how those files fit together.
For order data, request the order ID, location, date, item details, amounts, discounts, voids and refunds where available. Ask how partial refunds appear and whether modified or deleted transactions remain visible. For menus, ask whether modifiers and their prices are included in the same file as the items or in a separate file. For employees, ask how a staff ID connects time records to the correct person.
Identifiers matter when a record is spread across files. Request the keys that connect orders to payments and refunds, employees to shifts, and menu items to modifier groups. Also ask which fields cannot be exported, whether attachments or historical changes are excluded, and whether the provider charges for a custom export. Get the expected delivery date and cost in writing.
Keep the exit archive separate from the work of configuring a replacement restaurant POS. A historical export is evidence of past activity; your current, restaurant-approved menu is the reference for setting up today's prices and options. Neither should be assumed to replace the other.
Check sample files while the old account is open
Ask for representative samples early enough to correct problems. Open them using the software your team will actually use. Check that columns line up, dates are readable, special characters survived and amounts have the expected decimal places. Confirm that each file includes a header and that the data dictionary matches it.
Hypothetical example: A restaurant asks for one week's order detail. The old system shows 84 orders for the selected location and business-date range. The export contains 80 distinct order IDs. The manager checks whether the missing four are voided orders, orders from another location, or records excluded by the export settings. Until the difference is explained and corrected where necessary, the file is not an accepted handoff.
Counts alone are not enough. Select a few ordinary orders and a few exceptions, such as a discounted order and a partial refund. Compare their IDs, dates, line items and amounts with the old system. Check that a payment can be matched to the relevant order and that a settlement report can be understood alongside its transaction records. A sales total, a processing fee and a bank deposit are different measures; do not expect them to match without accounting for what each report includes.
For the menu, inspect an item with several modifiers and confirm that the item, options, prices and availability are understandable. For employee records, compare a small selection of shifts with the old system. Avoid circulating personal information in a general test folder; give only the people checking those records access.
These are file and record checks, not live-service tests. If you also evaluate a replacement system, use a simulation that cannot charge a real card, message a guest or dispatch a courier. A live service pilot is a separate decision with its own controls. Neither kind of test guarantees uninterrupted service during a changeover.
Document the cutoff and handoff
Before scheduling cancellation, ask the outgoing provider to put the important dates and conditions in writing. Contract termination, the last day to sign in, the last day to request an export and the end of support may be different dates. Ask whether any reports remain accessible afterward, who can access them and whether retrieval later has a fee.
Record these details in a handoff sheet:
- The contract end date and the deadline for cancellation notice.
- The final login and export-request dates, including any time zone.
- The records promised, date ranges, delivery method and expected delivery date.
- The person who will check each file and the person who will approve the handoff.
- The support contact, support end date and process for correcting a faulty export.
- The secure archive location, authorized users and recovery procedure.
Save the written terms and correspondence with the handoff sheet. Check your ability to open the archive from an authorized account before the old login ends. If the files are encrypted or password-protected, make sure an authorized backup person can obtain the key without relying on the departing provider's portal.
Decide what to do if a critical export is late or incomplete. For example, ask whether access can be extended and what that would cost. Do not schedule the cutoff on the assumption that a promised file will arrive complete on the last day. Hardware return and account access can have separate deadlines, so also confirm what happens to leased or purchased restaurant POS hardware.
Use the inventory in your next buying conversation
Give prospective providers the same list of records and operational requirements. Ask which historical files they can help you review, what information they need to configure your menu, and who is responsible for checking the result. Also ask how you would export your records if you left that provider later.
Compare the written operational quote totals as well as the handoff: include setup, recurring charges, processing, equipment and any stated exit or export fees that apply to your situation. Ask what is excluded and which charges can change. A low headline price does not answer whether you can retrieve your records when you need them. For more questions to bring to that conversation, see the related buying guide.
Take your inventory, sample-file criteria and proposed cutoff dates to a provider conversation. Discuss how Fleksa's restaurant management software would fit your requirements, and ask for the handoff responsibilities and any relevant costs in writing.
Frequently asked questions
What should I export before canceling a restaurant POS?
Start with order detail, menu records, employee and time records, and payment and settlement reports. Add other records your restaurant uses, such as gift card balances or reservations, and check which system holds each one.
Is a PDF sales report enough?
It may be useful as a readable summary, but it may not contain the detail or identifiers needed to sort and reconcile transactions. Ask for structured files and field definitions as well as reports.
When should I request the final export?
Request sample files well before cancellation and agree on a final export date with the provider. Leave time to check the files and resolve differences before login and support access end.
