Platform planning

Global Payments Retail Migration Guide

Confirm the account is Global Payments Retail / Heartland Retail rather than another product from the same payment provider.

Check my migration
Your next system

Moving into Global Payments Retail

Understand destination requirements before preparing your records.

Your current system

Moving from Global Payments Retail

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

Name the retail product and tenant

Bring the account URL, edition and locations. Payment-processing access alone is not access to the retail catalog. Legacy Heartland Retail help remains relevant to the retail product; confirm that its workflow applies to the tenant you use.

Use exports and mapping deliberately

The vendor documents item export and spreadsheet imports with field mapping. Preserve the original item identifiers and review update behavior before reimporting. Keep identifiers as text so long codes are not rounded or converted into scientific notation.

Separate items from purchasing and liabilities

Vendor instructions describe more than item imports, but each dataset has its own fields and relationships. Vendors, purchase orders, customer contacts and gift cards need individual decisions. A product vendor label is not proof that supplier terms or outstanding balances were retained.

Validate a real buying and selling example

Use an item with size/color variants, a supplier reference and stock in two locations. Include a partly received purchase order if required. Reconcile received and remaining quantities separately, and agree which records must stay in an archive.

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.