Portability must be tested, not assumed
The UK government's July 15 call for evidence on trusted data flows asks how organizations can access and share data with confidence. The UK Information Commissioner's portability guidance explains the value of structured, commonly used, machine-readable formats for covered personal data. The European Commission's July 16 data-sharing specification update adds a current example of how access rules, anonymization, eligibility, pricing, and security controls must be defined before a transfer process is operationally useful.
These rules do not define a restaurant's full contractual rights, and this guide is not legal advice. They do reinforce a migration principle: an export is useful only when authorized people can retrieve it, interpret it, reconcile it, protect it, and use it in the destination system.
Map the operating records and owners in the ServingIntel Genesis operating view.
The 12-export inventory
- Locations, revenue centers, terminals, and devices.
- Items, categories, menus, dayparts, and availability rules.
- Modifiers, recipes, combos, and kitchen-routing maps.
- Prices, taxes, fees, service charges, and effective dates.
- Orders, line items, timestamps, channels, and fulfillment states.
- Payments, tenders, tips, refunds, voids, and chargebacks.
- Employee, role, permission, and timekeeping records.
- Customer profiles and consent records where lawfully portable.
- Gift, stored-value, loyalty, promotion, and adjustment balances.
- Inventory, purchasing, receiving, transfer, and waste records.
- Audit logs, configuration history, and support records.
- Reports, attachments, images, and document indexes.
Start with the POS University evaluation guide to align the exit inventory with the requirements used to assess the next system.
Demand a data dictionary and control totals
For every file, document the field name, meaning, type, timezone, units, enumerated values, relationships, history window, and known omissions. Record row counts and financial control totals by location and period. A CSV that opens is not necessarily a complete or correctly interpreted record.
Use ServingIntel solutions to identify the operational systems that consume or produce the records, then assign one accountable owner to each interface.
Run a dry export before notice
Request a representative extract while the relationship is normal. Store it in an approved restricted location. Test encoding, timestamps, identifiers, line-item relationships, negative values, attachments, and the ability to import or query it independently. Log elapsed time, manual intervention, vendor dependencies, and unresolved gaps.
The Support4POS outage playbook supplies a companion continuity model for operating while integrations or historical records are temporarily unavailable.
Protect people and payment data
Minimize the export to authorized business needs, use encrypted transfer and storage, separate duties, log access, verify retention, and define secure disposal. Never move raw payment credentials or unrelated personal data merely because the source system can produce it. Escalate scope and security questions through ServingIntel support resources.
Set migration acceptance gates
- All 12 domains are exported or have a documented, accepted exception.
- Field mappings and effective dates are reviewed by business owners.
- Control totals reconcile across source, staging, and destination.
- Critical attachments and audit trails remain discoverable.
- Security, retention, consent, and deletion duties are assigned.
- A rollback or read-only archive path exists for disputed records.
Follow migration and operating context through ServingIntel News & Insights, and document device and archive requirements in the cutover record.
The bottom line: do not give notice with only a promise that data can be exported. Leave with a tested file set, documented meaning, reconciled totals, controlled access, and named acceptance owners.
