Identify the system that owns the records
Record the actual business application behind the TCx estate. A TCx device, retail operating system and commerce application can refer to different layers.
Platform planning
Toshiba TCx Migration Guide
Record the actual business application behind the TCx estate. A TCx device, retail operating system and commerce application can refer to different layers.
Check my migrationMoving into Toshiba TCx
Understand destination requirements before preparing your records.
Your current systemMoving from Toshiba TCx
Start with your edition, available exports, and the data you need.
Confirm the actual extraction and receiving interfaces
Toshiba’s operating-system information identifies TCx Sky and other platform components. It is not a retail database schema. Ask the software/estate owner which application and central service hold merchandise, customers and stock.
Relationships to inventory before booking
- Hardware/OS versus retail software identity
- Central merchandise and store/offline data copies
- Customer and inventory authoritative services
- Deployment and support ownership across the estate
Prepare a representative acceptance case
Use an item visible at two TCx-equipped checkouts whose master record is held in a separate central application. 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
Identify actual POS/back-office application, release and data owner before selecting a method. Obtain its authorized schema and extraction/loading interfaces; hardware or OS branding is insufficient.
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.
Official references
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.