Migrating customer data from NCR Retail Online

NCR Retail Online was built to connect ecommerce activity with retail inventory, customer records, orders, and business management workflows. Since the platform has been discontinued, merchants need a controlled path to move essential information into a replacement system rather than treating the change as a simple storefront redesign. Learn more about Fine China.html.

A successful transition protects customer history while giving the new platform clean, usable data. Magento and WooCommerce are common alternatives available through NCR Counterpoint partners, but the correct destination depends on catalog size, store integrations, reporting needs, fulfillment processes, and the technical support available to your team.

Customer data migration should therefore be handled as a documented project. The checklist below covers preparation, extraction, privacy, field mapping, testing, launch, and long-term recordkeeping so that important information does not disappear during the platform change.

Confirm the migration scope and ownership

Start by identifying every data source connected to NCR Retail Online. The ecommerce database may contain customer profiles, addresses, order history, product reviews, discount records, gift card activity, newsletter subscriptions, and account credentials. Related information may also exist in NCR Counterpoint, payment gateways, shipping tools, email services, or spreadsheets maintained by staff.

Create a written inventory of what must move, what can be archived, and what should be rebuilt manually. Assign an owner for each category, such as customer accounts, product data, financial records, integrations, and compliance. This prevents assumptions that a partner or developer will automatically migrate information that was never included in the project brief.

Decide whether the replacement store will preserve customer login accounts. Passwords are often stored as protected hashes that cannot be transferred between systems. If direct migration is impossible, plan a secure password reset campaign and explain the change clearly to customers without exposing confidential account details.

Capture the source data safely

Before exporting anything, create a full backup of the NCR Retail Online environment and any connected systems. Retain the original files in a restricted location, record the export date, and document the file formats and filters used. A backup gives the team a reference point if records are missing, altered, or incorrectly transformed during testing.

Export customer information in separate, clearly named files where possible. Typical extracts include customer IDs, names, email addresses, telephone numbers, billing addresses, shipping addresses, marketing permissions, order headers, order lines, refunds, tax details, and loyalty balances. Keeping different datasets distinct makes validation easier than placing every field into one large spreadsheet.

Do not export payment card numbers, security codes, or other prohibited payment credentials into ordinary migration files. Payment tokens can usually be moved only through an approved gateway or processor procedure. Ask the payment provider and implementation partner how recurring payments, saved payment methods, refunds, and chargeback references should be handled.

Clean records before field mapping

An old retail database often contains duplicate customers, incomplete addresses, outdated email accounts, test orders, abandoned registrations, and inconsistent formatting. Cleaning these records before import reduces duplicate accounts and makes future search, segmentation, and customer service more reliable.

Use a stable matching strategy based on several fields rather than email address alone. A shared email may belong to a household, while a changed email may hide two records for the same person. Compare customer IDs, names, phone numbers, addresses, order history, and account status, then send uncertain matches to a human reviewer.

Preserve original identifiers in a dedicated field. The legacy customer ID and order number can be valuable when staff need to investigate a historical purchase or reconcile a refund. Avoid overwriting these references with newly generated IDs from Magento, WooCommerce, or another destination platform.

Map fields and test transformations

Field mapping translates the old data model into the structure required by the new ecommerce system. Document the source field, destination field, transformation rule, acceptable values, and owner for each important attribute. Include examples for dates, currencies, tax rates, order statuses, address formats, and marketing consent.

The following mapping reference can help organize a migration workbook:

Run a small pilot import before moving the full dataset. Select representative customers and orders, including guest checkouts, international addresses, refunds, discounts, tax-exempt transactions, and products with variations. Review the results in the new administration area and on the customer-facing storefront.

Compare record counts before and after the pilot. Check whether names display correctly, totals remain accurate, order dates use the right time zone, and product images or downloadable assets still work. A technically completed import can still be commercially wrong if order totals, fulfillment statuses, or customer permissions have been changed.

Protect privacy throughout the transfer

Customer information should be treated as confidential from export through deletion. Limit access to the migration team, use encrypted storage, and transfer files through secure channels rather than ordinary email attachments. Keep a simple access log showing who handled the files and when.

Review retention obligations before deciding what to import. A customer may need to remain in financial records for tax or accounting purposes even when marketing data should be removed. Separate transactional history from promotional subscriptions so that a customer who has withdrawn consent is not accidentally added to a new mailing list.

Review the destination platform’s security controls, administrator permissions, backup policy, and breach notification process. Enable multifactor authentication, remove temporary accounts after implementation, and avoid giving every store employee unrestricted access to personal information.

Rebuild connected retail operations

Customer records are only useful when the surrounding retail workflows function correctly. Reconnect inventory synchronization, tax calculation, shipping rules, payment processing, returns, email notifications, analytics, and accounting exports. If the business operates physical stores through NCR Counterpoint, verify how online orders and customer updates will flow between the new store and retail system.

Review customer-facing content as part of the rebuild. Product descriptions, category pages, store policies, and promotional materials may need fresh links and updated checkout instructions. Historical merchandising categories can also reveal customer preferences; for example, an archived collection of gift card options may indicate a product type that needs a dedicated equivalent in the replacement store.

Test the complete purchase journey from account creation to fulfillment and post-purchase service. Place orders using different payment methods, apply discounts, request returns, and verify that inventory changes in the intended location. Include a test involving a physical-store associate if online and in-store operations are connected.

Control the launch and preserve history

Choose a cutover window that avoids peak trading periods and allows the team to pause changes in the old system. Take a final incremental export, reconcile new orders created since the pilot, and place the legacy storefront into maintenance mode if necessary. Record the exact time at which the old system stopped accepting changes.

After importing the final files, compare totals for customers, orders, products, refunds, and gift certificates. Sample records across different years and locations, then ask customer service staff to verify that they can find order history and resolve common account issues. Monitor failed emails, payment errors, stock discrepancies, and duplicate accounts closely during the first days after launch.

Maintain a read-only archive of the original exports, migration logs, field mappings, error reports, and approval records. Store it according to the organization’s retention policy and restrict access. Do not delete the legacy data immediately; wait until reconciliation is complete and any legal, accounting, or customer-service requirements have been addressed.

Migration controls worth keeping

A concise control list helps teams maintain discipline after the technical work begins:

• Assign one accountable owner for each dataset and integration.
• Keep an untouched source backup and a separate working copy.
• Test with a representative sample before the full import.
• Reconcile record counts, financial totals, and consent statuses.
• Document failed rows, corrections, approvals, and final cutover times.

A post-launch review should happen after the first week and again after the first full reporting period. Compare sales, order fulfillment, customer account activity, email delivery, and inventory balances with the legacy system’s final reports. Investigate variances while the migration details are still fresh.

The move away from NCR Retail Online is complete only when customers can shop, receive service, and manage their information without losing meaningful history. Use the checklist as a working document, involve your NCR Counterpoint partner early, and begin with a controlled data audit before selecting the final import date. A careful migration creates a dependable foundation for the new Magento, WooCommerce, or partner-supported retail environment.