Platform planning

Celerant Migration Guide

Name the Celerant product and implementation owner before treating a data conversion as part of the wider launch.

Check my migration
Your next system

Moving into Celerant

Understand destination requirements before preparing your records.

Your current system

Moving from Celerant

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

Distinguish the product and project

Identify Cumulus Retail, Stratus Enterprise, version and custom modules. A vendor-managed Celerant upgrade is different from a move between Celerant and another POS. Ask which conversions are included in the vendor implementation and which work would be assigned to Sqquid.

Agree who prepares and imports each dataset

Celerant describes implementation management and optional data conversion. That overview does not provide a universal third-party import specification. Obtain the receiving field requirements and an authorized source extract for the actual project before accepting the method.

Separate shared retail operations

Map size/color items, location stock and the customers used by ecommerce. Review purchasing, special orders, rewards and custom fields individually. Do not assume that a shared database guarantees equivalent records in another system.

Use an acceptance record across teams

Choose one full style, an existing online item and an open purchasing commitment. Have the retailer and implementation owner approve the map, exceptions and snapshot. Hardware, training, custom modules and ongoing integrations remain separate responsibilities.

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.