Platform planning

Revel Systems Migration Guide

Identify the establishment, Management Console version, retail versus restaurant configuration and account support contact. Current service status is not evidence of a migration interface or new-account availability.

Check my migration
Your next system

Moving into Revel Systems

Understand destination requirements before preparing your records.

Your current system

Moving from Revel Systems

Start with your edition, available exports, and the data you need.

Identify the system that owns the records

Identify the establishment, Management Console version, retail versus restaurant configuration and account support contact. Current service status is not evidence of a migration interface or new-account availability.

Confirm the actual extraction and receiving interfaces

Revel’s indexed help describes matrix import, but the checked article rendered an incomplete help shell. Obtain the current applicable matrix and customer specifications through the customer’s authorized support access before relying on a cached description.

Relationships to inventory before booking

  • Matrix parents and sellable attribute combinations
  • Establishment/store scope and inventory quantities
  • Customer identities and separately owned reward providers
  • Retail merchandise versus ingredients/modifiers

Prepare a representative acceptance case

Use a matrix item, a customer with rewards in an external provider and stock in two establishments. Keep the source IDs, expected grouping and location state with the proposed destination result. Check the relevant relationships instead of accepting only a record count.

Resolve the method before accepting the project

Confirm current edition/commercial availability, accessible export/import instructions, matrix/customer identity rules and authorized account access. The public matrix article could not be fully verified in this review.

Use the access guide to arrange secure customer-authorized access and the testing guide to define evidence. History, gift cards, balances and ongoing integration need separate decisions.

Migration scope and responsibilities

The standard migration fee is $2,999 USD for the confirmed scope.

Access to both systems

You must provide Sqquid full authorized access to both systems and be able to access your own data. Arrange access through an agreed secure process. Do not put passwords, API tokens, payment information or customer export files into the general enquiry form.

Source data quality

Sqquid is not responsible for migration errors caused by poor data supplied by the customer. Source issues, proposed corrections and exclusions need to be recorded before the transfer is accepted.

Earlier work and guarantee limits

Sqquid does not guarantee a migration that started before Sqquid was hired. Any guarantee is limited to the data migration work performed by Sqquid and expires on the launch date. Record the agreed launch milestone in the written scope; do not assume post-launch guarantee coverage.

Vendor charges and separate work

Vendor charges are passed to the customer in addition to the confirmed migration fee. POS implementation, hardware, payment setup, staff training and ongoing integrations have separate responsibilities and scope. A Sqquid software subscription is not required for the migration service.

Your systems. Your next chapter.

Retail details, carefully reviewed.

Tell us where your data is today, and where you’d like to go. We’ll help you understand the next step.

Check my migration Retail data migration for $2,999. Scope confirmed before booking.