Migrate NCR product images and galleries without losing ALT text

NCR Retail Online was an e-commerce software platform designed to connect online stores with retail inventory and business management systems. Its discontinuation has prompted Australian merchants to transition through NCR Counterpoint partners to alternatives such as Magento or WooCommerce. Moving a storefront involves more than recreating products: identifiers, gallery order, image locations, variants and accessibility metadata must continue to match the source catalogue.

Migrating NCR’s product images and galleries while preserving ALT text should therefore be treated as data governance, not a last-minute file upload. Shoppers in Sydney and Melbourne commonly compare products on a phone while commuting, and shoppers in regional Australia often need a clear view of dimensions, colour and condition before committing to delivery across long distances. Useful alternative text supports screen-reader users and reinforces the visual information expected by a broad online audience.

Build a media inventory before changing platforms

Begin with a media inventory that joins every source asset to a product, SKU and variant. Record the original URL, filename, format, dimensions, gallery position, image role and ALT-text status before exporting anything. Flag missing images, duplicate photographs, mismatched product codes and galleries that rely on filenames alone. This reveals whether the catalogue can be migrated as a clean relationship or needs manual correction first.

A SKU-level migration planning approach also exposes dependencies that product-level lists can hide, such as a shared colour swatch serving several variants or an image attached to the parent product while gallery slots belong to individual sizes. Keep the source export read-only, assign stable internal IDs and store the relationship between old and new identifiers. That audit trail makes reconciliation possible and gives support partners a precise object to investigate.

Protect ALT text as governed catalog data

ALT text is not a caption, filename or SEO keyword field. It should communicate the purpose of an image when that information is not already available in nearby copy; decorative images may correctly use an empty value. Record whether each entry describes the full image, a close-up, a scale reference, a colour option or another function. Those labels help reviewers decide what can transfer unchanged and what needs rewriting for the new theme.

For Australian retailers, accessibility is both an inclusion priority and a risk-control issue. Australian Government services and many state agencies work to WCAG 2.2 AA, while private retailers are not governed by one universal Australian web-accessibility rule. The Australian Consumer Law still applies to advertising and product representations, so image descriptions must not contradict the item offered. Migration records containing staff names or customer identifiers may also fall under the Privacy Act 1988.

Map the ALT field explicitly in both systems rather than assuming an import will recreate it. Magento and WooCommerce may expose image metadata through different fields or extensions, and a successful file transfer can still leave the descriptive text behind. Retain the original wording beside any revised version, record the reason for each change and involve an accessibility reviewer when the text conveys size, material, colour or product state.

Move images and videos through controlled tests

Move assets through a controlled pipeline that can validate counts and checksums before the new store goes live. Transfer the full-resolution master separately from generated thumbnails, retain the source URL map and use permanent, descriptive filenames for new assets. Redirect obsolete image URLs to their closest equivalents and update the image sitemap. Search visibility can deteriorate quickly when an apparently successful migration leaves hundreds of product images returning broken responses.

Use a staging environment to test representative SKUs rather than trusting a bulk upload report. For galleries containing video, planning around mixing media codecs helps avoid playback gaps caused by unsupported combinations, container formats or browser-specific behaviour. Confirm that each gallery item has a poster image, sensible fallback and accessible description, and that the chosen codec works on the devices Australian customers actually use.

Performance matters because mobile connections and regional bandwidth vary. Convert suitable still images to modern formats while keeping a broadly compatible fallback, set sensible dimensions to prevent layout shifts and avoid autoplay for video with sound. A polished product page should remain usable on an older handset and a constrained connection, not only on the fast office network where the migration was assembled.

Select a migration route by cost and complexity

Choose the operating model before assigning internal effort. During evaluating third-party integrations, compare what each connector transfers, what it merely references, who owns the mapping rules and who provides support after launch. An integration that synchronises product records but omits gallery order or ALT text is not complete. Document update frequency, failure reporting and security controls as contract requirements rather than informal assumptions.

Three practical routes suit different catalogue sizes and internal capabilities:

Estimate the whole operating burden, including reconciliation, retouching, redirects, extension maintenance and accessibility review. Australian merchants should also test tax, currency and fulfilment assumptions: stores commonly sell in Australian dollars with GST-inclusive prices, and connectors may need to preserve integrations with Australia Post or local fulfilment tools. A platform that handles files well but changes product data can create costly downstream work.

Complete a production-ready quality check

Run the final check as a repeatable release gate, with product owners, developers and an accessibility reviewer signing off the same sample. Test source-to-destination counts, rendered pages and actual downloads instead of relying only on an import summary. Keep the original media export and migration log for the agreed retention period, with access limited to staff who need it.

• Reconcile every SKU and variant against source asset counts, including empty galleries and duplicate images.
• Compare primary images and gallery sequence, then confirm that variants display the intended colour or size.
• Check ALT text for presence, purpose and contextual accuracy without generating identical descriptions for every product.
• Review decorative images separately so meaningful images are described and purely decorative ones are not announced.
• Test pages with a keyboard, screen reader, mobile browser and reduced-data connection.
• Verify image URLs, redirects, thumbnails, downloads and the image sitemap in the staging environment.
• Record exceptions, corrections, approvals and source-to-new IDs in one auditable migration log.

Approve production only after remaining exceptions have named owners and due dates, then watch error logs and search indexing after release. The next concrete step is a 20-SKU pilot from one category: export those products, inventory every image and ALT entry, and record the source-to-new mapping before full-catalogue processing.