Identify the system that owns the records
Name the retail product, version, tenant, legal entities and countries. Keep the entity that owns a customer or stock record explicit before considering consolidation.
Platform planning
Cegid Retail Migration Guide
Name the retail product, version, tenant, legal entities and countries. Keep the entity that owns a customer or stock record explicit before considering consolidation.
Check my migrationMoving into Cegid Retail
Understand destination requirements before preparing your records.
Your current systemMoving from Cegid Retail
Start with your edition, available exports, and the data you need.
Confirm the actual extraction and receiving interfaces
Current vendor material identifies Retail Y2 but does not establish an account-specific migration interface. Vendor certification or hosting assurances are not a certification of Sqquid or proof of data portability.
Relationships to inventory before booking
- Entity/store identifiers and currency context
- Merchandise and price ownership across countries
- Customer identities and separately held liabilities
- Fiscal records and locally owned configuration
Prepare a representative acceptance case
Use a shared product sold by two entities, with separately owned stock and customer credit. 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
Obtain exact product/tenant interface documentation, entity/store crosswalks and approved access; confirm data residency and country-specific implementation responsibilities with the estate owner without inventing compliance coverage.
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.