Platform planning

Microsoft Dynamics RMS Migration Guide

Start with the surviving RMS environment and its readable records before selecting a new POS.

Check my migration
Your next system

Moving into Microsoft Dynamics RMS

Understand destination requirements before preparing your records.

Your current system

Moving from Microsoft Dynamics RMS

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

Recognize the legacy support boundary

Microsoft lists extended support for Dynamics Retail Management System 2.0 as ending July 14, 2021, covering Store Operations and Headquarters. RMS is not Dynamics 365 Commerce or Business Central. Do not apply another Dynamics product’s migration instructions to an RMS database.

Preserve the environment that reads the records

Identify the store databases, Headquarters database, installed version and person authorized to access them. Keep a protected backup and verify that the available environment can retrieve a known item, customer and receipt. A database filename alone is not a usable archive.

Resolve store and headquarters differences

Compare a store’s stock with consolidated totals and identify delayed updates or conflicting identifiers. Agree which snapshot owns opening inventory. Review custom fields, receivables and gift cards independently of a core product/contact transfer.

Plan an outbound sample and archive

Ask the support partner for an authorized extraction suitable for the installed deployment. Map a complete variant family and stock at each store to the chosen destination. This guide does not recommend a new RMS installation or promise native historical import elsewhere.

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.