Move historical records into your new POS when staff need them in daily work and the provider can import them in a useful, verifiable form. Keep records needed only for occasional review in an accessible archive. Some records may need both: a limited import for current work and a complete export for reference.
The decision turns on use, not age alone. A customer record that helps staff answer a current inquiry may be worth importing. Five years of closed checks may be easier to preserve outside the POS, provided someone can find and understand them when needed.
Start with the questions old records must answer
Before asking a provider to import everything, list the decisions and inquiries your restaurant expects to handle. For each one, name the person who needs the answer, how quickly they need it, and the details they must see.
Management comparisons. Owners may want to compare sales by day, location, item, or service period. Decide whether a monthly summary is enough or whether managers need individual checks and modifiers. Also ask whether old and new reports use the same definitions. A change in item names, service periods, or location codes can make a comparison misleading even when both totals are correct.
Customer inquiries. A guest may ask about an earlier order, a refund, or a stored account. Identify which fields would help staff locate the record: order number, date, location, and customer identifier, for example. Decide who may see that information and whether it must be available at the counter or can be retrieved by a manager from an archive.
Accounting review. Your bookkeeper may need sales summaries, payment breakdowns, adjustments, and supporting transaction details. Ask which reports and supporting records they actually use. A new POS dashboard is not automatically a substitute for the original reports or exports.
Ongoing relationships. Customer profiles, gift card balances, and loyalty records can affect future service. Treat each as a separate migration decision. Ask the provider which fields and balances it can accept, how they would appear, and how staff could verify them. An exported balance is not the same as a balance a guest can redeem in the new system.
Choose a destination for each record type
Use the matrix below as a starting point, not as a retention schedule. The choices assume a single-location restaurant whose managers review old sales monthly, while front-counter staff handle current customer inquiries. Your needs may differ.
| Record | Likely destination | Decision check |
|---|---|---|
| Recent customer profiles | Import selected fields; retain an export | Can staff find the right profile without creating duplicates? |
| Closed checks and order details | Searchable archive | Can a manager find a check by date, location, or order number? |
| Sales and payment summaries | Archive; import only if useful for reporting | Can the new reports separate historical figures from new activity? |
| Gift card and loyalty balances | Evaluate for import and redemption; retain a reference export | Can each balance be matched and used as intended after a simulated check? |
| Old menu and item codes | Archive with transaction records | Can reviewers interpret old item names and codes later? |
The matrix favors an archive for closed checks because the assumed restaurant needs occasional management access, not counter-level access to every old transaction. It favors evaluating customer profiles for import because staff may need them during service. Neither choice removes the need for a complete, readable reference copy.
An import is useful only if the new system gives the record a practical job. Ask whether staff can search it, whether it appears in the right screen, and whether reports can use it without mixing it into current-period activity. A provider may accept a file but import only certain fields, date ranges, or record types. Get those limits in writing before deciding what to move.
An archive also needs more than a folder labeled “old POS.” Choose a format the assigned users can open and search. Keep a description of each file, its date range, field names, and any codes needed to interpret it. If a file contains several locations or service types, explain how to distinguish them. Preserve supporting reports alongside the detailed records so reviewers have context.
Ask how exports handle attachments, adjustments, and relationships between records. A spreadsheet of order headers without its line items may answer some sales questions but not a guest's question about what was ordered. Likewise, a customer list without a reliable identifier may be difficult to match to historical orders.
When comparing restaurant management software, bring a short list of the questions staff must answer after the switch. Have each provider show where those answers would be found, including when the answer remains in an outside archive.
Check identifiers, relationships, and totals
Run a reconciliation on a sample period before approving the full approach. First save the source reports and exports for that period. Then compare them with the imported records or archive files, using the same date range, location, and definitions. Record any differences and their explanations.
Hypothetical example: A restaurant selects one closed week at one location. Its source report shows 240 closed checks and $6,000 in gross sales. It also shows $300 in refunds, leaving $5,700 after refunds for this comparison. The exported detail contains 240 checks totaling $6,000 before refunds and separate refund records totaling $300. The counts and amounts agree for the stated measures.
That agreement is a starting point, not proof that every detail survived. The owner should also inspect several individual checks, including a refunded order, and match their order numbers, dates, items, and refund references. Payment processing fees are not included in these sales figures; they are a separate measure. The example is a record reconciliation, not an operating-cost calculation.
Use a short checklist for the sample:
- Identifiers: Check that order, customer, location, and item identifiers remain present or have a documented mapping. Look for duplicates and missing links.
- Dates and boundaries: Confirm the business-day cutoff, time zone, and date range used on both sides. A late-night check can otherwise appear in a different day.
- Amounts and adjustments: Compare the same measures separately, including sales, refunds, and payment breakdowns. Do not assume one report's total means the same thing as another's.
- Relationships: Open a few orders and verify that their line items, modifiers, payments, and adjustments connect to the right check.
- Usability: Ask an authorized manager to find a sample record using the archive instructions, then compare it with the source record.
For balances or other records that could affect a guest, use a simulated check in an isolated practice environment agreed with the provider. It must not trigger a real card payment, guest message, or courier dispatch. Confirm separately with the provider how any live balance will be verified before staff rely on it. A simulated check is not a live service pilot.
If the sample differs, pause and identify whether the cause is a missing field, a changed definition, a date boundary, or an actual missing record. Agree who will correct it and repeat the check. Keep the source material accessible while discrepancies are resolved; do not assume a switch will be uninterrupted or that every historical record will transfer.
Assign archive access and ongoing ownership
Give one person responsibility for the archive, with a named backup. That owner should know where the files live, what each contains, how to restore a copy, and whom to contact if a file cannot be opened. Store the instructions where the backup can find them, not only in the departing manager's inbox.
Limit access according to the work people perform. A bookkeeper may need reports and transaction details; a shift manager may need a narrower way to look up a guest inquiry. Decide how requests are made and who can retrieve sensitive records. Keep a separate backup and periodically have an authorized person open a sample file and locate a record.
Ask qualified advisers about current retention requirements and the appropriate treatment of your records and contracts. Then document your restaurant's retention and deletion decisions. Do not delete the old copy simply because an import appears in the new POS; first resolve the sample checks and confirm that the archive can be opened and understood.
Include the work in your buying discussion. Ask for a written quote that separates migration setup, recurring software charges, and any archive or export assistance. Ask what happens if additional mapping or a second import is needed. For a broader look at quote trade-offs, see the related buying guide. If a change also involves terminals or printers, review the restaurant POS hardware separately; hardware decisions do not establish what historical records can be imported.
Next, select one record type and one closed sample period. Write down its destination, required fields, owner, and reconciliation checks. Bring that sheet to a restaurant POS provider and ask them to confirm the import limits and demonstrate the intended lookup.
Frequently asked questions
Should every old transaction be imported into the new POS?
No. Import transactions when staff need them there and the provider can make them searchable and useful. Otherwise, a well-documented archive may serve occasional inquiries and reviews better.
Is a sales summary enough to preserve order history?
Not necessarily. A summary can support broad comparisons, but it may not show individual items, modifiers, payments, or refunds. Decide which questions require transaction-level detail before choosing what to keep.
Who should verify the migrated records?
Assign a restaurant owner or manager to coordinate the check, with the bookkeeper and provider involved where relevant. Compare a defined sample against source reports, document discrepancies, and confirm corrections before relying on the records.
