Platform planning

Paladin POS Migration Guide

Capture the intended Paladin inventory scope before using a spreadsheet as the migration source.

Check my migration
Your next system

Moving into Paladin POS

Understand destination requirements before preparing your records.

Your current system

Moving from Paladin POS

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

Review the export selection

Paladin documents inventory export through Data Viewer, with choices including active inventory, supplier filters and deleted items. Save the selected coverage and verify expected counts. An active-stock export and a wider catalog/archive are different deliverables.

Preserve purchasing and selling units

Identify each-unit, pack and bulk-unit products with distributor codes and costs. Keep the supplier’s ordering reference separate from the checkout barcode. Agree conversions rather than assuming a numeric stock value represents the same unit in the destination.

Keep customer accounts outside the catalog assumption

House accounts, outstanding debt, credits, gift cards and historical receipts need separate extraction and receiving plans. Specialized modules or distributor connections also need named owners; an exported inventory file does not recreate those workflows.

Validate the hardware-store example

Choose a bulk-unit product, a supplier-linked item and a customer with an account balance. Compare the item’s receiving identity and location quantity, then check the account outcome independently. Preserve source access and do not promise a full database conversion from an inventory export.

Migration scope and responsibilities

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

Tailored to your retailer data

Every migration is unique. Your catalog, barcodes, orders and customer information are unique and proprietary to your business. We work closely with you to tailor the migration for the best possible outcome, agree the included records and define acceptance checks for your stores.

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.