Migrating From NCR To Magento With Gift Cards And Store Credit

When NCR Retail Online was discontinued, retailers using its ecommerce tools had to move their online operations to another platform. Magento, now available as Magento Open Source or Adobe Commerce, is a common destination for businesses that need flexible catalog management, integrations, and control over customer accounts. Learn more about Accessories.html.

Gift cards and store credit deserve special attention during that move. Product pages and order history can often be transferred through standard export files, but financial value is more sensitive. A missing balance, duplicated code, incorrect expiration date, or broken redemption rule can create customer complaints and accounting problems.

A successful migration treats stored value as a controlled financial data project rather than a routine catalog import. The objective is to preserve what customers are entitled to use while keeping balances secure, auditable, and compatible with Magento’s checkout and refund processes.

Define The Stored Value Scope

Start by separating every type of value managed in the NCR environment. Physical gift cards, digital gift certificates, promotional credits, loyalty rewards, refunds issued as store credit, and manually adjusted account balances may have different rules. Combining them into one generic “credit” field can make later reconciliation difficult.

For each record, document the card or account identifier, customer association, original amount, current balance, currency, activation status, issue date, expiration date, and transaction history. Also record whether the value can be used online, in physical stores, or across both channels. A card that works at a retail register may require a connector before it can be redeemed in Magento.

The same inventory and customer audit should cover products and content that support gift-card sales. If your team is also moving editorial material, the guidance on content migration planning can help separate page content from transactional records. Keeping these workstreams distinct reduces the risk of treating a blog export as if it were a financial ledger.

Choose A Magento Stored Value Model

Magento does not automatically reproduce every NCR gift card or store-credit behavior. Your implementation may use native Adobe Commerce capabilities, a vetted Magento extension, a payment provider’s gift card service, or a custom integration with the Counterpoint and retail point-of-sale environment.

The correct choice depends on how the business operates. A retailer selling digital cards online may need immediate code generation, customer email delivery, partial redemption, and balance lookup. A business with physical cards may need barcode support, activation at checkout, reloads, replacement cards, and shared balances between stores and the website.

Store credit should be evaluated separately from gift cards. It is usually attached to a customer account rather than represented by a transferable code. Confirm whether Magento will issue credit for returns, allow administrators to adjust balances, support partial payment, and display available credit in the customer account. These rules should be written into the functional specification before development begins.

Map Data Without Losing Value

Create a field-level migration map before exporting anything. A gift card code may need a unique identifier, encrypted or tokenized representation, balance, status, and website scope. A store-credit record may require a customer ID, currency, balance, source, adjustment reason, and timestamp. Do not assume that a column called “amount” has the same meaning in both systems.

Customer matching is one of the highest-risk steps. Email addresses may have changed, duplicate accounts may exist, and some cards may be anonymous. Use a stable legacy customer reference where possible, then apply carefully reviewed matching rules. Unmatched balances should enter an exception queue instead of being silently discarded or assigned to the wrong account.

Preserve the transaction trail, not just the current balance. A balance without its underlying issuance, redemption, refund, and adjustment history is harder to investigate. For larger migrations, load historical transactions into a separate archive or reporting store if the selected Magento solution cannot retain them natively. This provides an audit reference without overloading the live checkout database.

Reconcile Balances And Security Controls

Before the final import, calculate the total outstanding liability in the NCR system. Group the result by card type, currency, status, sales channel, and expiration period. Then compare it with the totals produced by the Magento staging import. Any difference should be explained through a documented rule, such as expired cards excluded by policy or cancelled orders returned to available credit.

Security controls are essential because gift-card numbers can function like cash. Never place full codes, PINs, or sensitive tokens in ordinary spreadsheets, email attachments, test screenshots, or publicly accessible backups. Use encrypted transfers, restricted administrative access, and separate credentials for migration tools. If codes must be rehashed or tokenized, confirm that the chosen extension can still validate them during redemption.

Refund behavior requires a dedicated review. Test refunds to the original payment method, refunds to store credit, partial refunds, cancelled orders, and returns after a gift card has been partially used. The financial system, Magento order record, and retail point of sale should agree about the resulting liability.

Test Real Customer Journeys

Testing should use realistic scenarios rather than a simple successful checkout. Load masked production-like data into a staging environment and verify new card issuance, account credit, balance lookup, partial redemption, mixed payment, cancelled orders, tax calculation, shipping charges, and abandoned carts. Include customers with multiple cards and accounts with zero or negative adjustments where the business rules permit them.

Review the storefront experience on desktop and mobile. Customers should understand where to enter a gift-card code, how much remains after a purchase, and whether store credit is automatically applied or selected manually. Transactional emails should show enough information to be useful without exposing more code data than necessary.

Catalog and content checks still matter because customers may buy cards from category or landing pages. Test internal links, images, pricing, and availability alongside financial functions; even a merchandising page such as barware products can reveal broken redirects or incomplete catalog mappings after the platform change. Keep the test data clearly marked so it cannot be mistaken for live value.

Coordinate The Cutover

Choose a cutover window that limits new gift-card sales and store-credit adjustments while the final export is prepared. A brief transaction freeze is usually safer than trying to reconcile simultaneous changes from NCR and Magento. If a freeze is impossible, capture a final delta file containing cards issued, redeemed, refunded, or adjusted after the first migration run.

Assign owners for ecommerce, finance, retail operations, customer service, and technical support. Customer service staff need a reliable procedure for checking balances, handling unmatched accounts, and escalating disputed value. Store associates also need clear instructions if the new platform changes barcode scanning, activation, or redemption behavior.

Keep the legacy system available in read-only form for an agreed retention period. It can provide evidence for historical disputes and help explain balances that customers question after launch. Update privacy, retention, and access policies so archived exports are protected and eventually removed according to legal and business requirements.

Use A Controlled Migration Checklist

A short operational checklist helps turn the migration plan into verifiable work:

• Inventory every gift-card, certificate, and store-credit source, including spreadsheets and point-of-sale records.
• Approve the Magento extension or integration and document its balance, refund, expiration, and omnichannel rules.
• Reconcile imported balances against NCR totals before enabling customer redemption.
• Run security, checkout, account, email, refund, and POS tests with representative scenarios.
• Train finance, support, and store teams on exceptions, adjustments, and post-launch reporting.

After launch, monitor redemption failures, duplicate-code alerts, refund discrepancies, and unusual balance adjustments daily. Compare Magento activity with payment and retail systems during the first settlement cycles. Early monitoring can identify an integration issue before it affects a large number of customers.

A carefully managed move from NCR to Magento preserves more than product data. It protects customer trust, keeps outstanding liabilities visible, and gives the business a dependable foundation for future ecommerce changes. Review your stored-value inventory, approve the target rules, and begin with a staged migration that can be reconciled before customers are redirected to the new storefront.