Moving product images and descriptions from NCR

Migrating a retail catalog from NCR Retail Online involves more than copying product names into a new store. Product images, descriptions, pricing fields, variants, categories, search data, and merchandising relationships all need to arrive in the replacement platform with their meaning intact. A careful process protects organic visibility and gives shoppers the same clear buying experience after the change.

NCR Retail Online was discontinued, so merchants moving to platforms such as Magento or WooCommerce through NCR Counterpoint partners must treat the work as a structured catalog migration. The exact tools may vary, but the core principles remain consistent: preserve the source data, improve weak content while it is being moved, and validate the result before changing domains or sending customers to the new storefront.

The strongest migration projects begin with an inventory of what exists. That inventory becomes a working reference when an export contains unclear fields, duplicate images, incomplete descriptions, or products that should no longer be sold.

Assess the catalog before exporting

Start by recording the number of products, categories, variants, images, and content fields in the NCR store. Identify which products are active, hidden, discontinued, seasonal, or duplicated. This prevents obsolete merchandise from being transferred automatically and helps establish a realistic scope for the project.

Review how descriptions are currently written. Some may contain formatting that the new platform cannot interpret, while others may rely on short descriptions, specifications, or custom fields that have no direct destination. Examine category placement as well, particularly where products overlap. For example, reviewing existing barware examples can reveal whether product taxonomy is broad enough for shoppers to browse naturally.

Create a content audit spreadsheet with a row for every product and columns for the current SKU, product name, brand, category, description, image filenames, image URLs, variant data, price, stock status, and destination URL. Add columns for missing information and migration decisions. This document acts as both a cleanup tool and a quality-control record.

Export product information safely

Use the most complete export available from NCR or your Counterpoint migration partner. A basic product export may omit image relationships, long descriptions, custom attributes, or variant combinations. Request separate files when necessary, and keep the original exports unchanged in a secure, dated folder.

Images should be downloaded in their original resolution rather than copied from browser previews. Preserve the connection between each image and its SKU, variant, or color option. If filenames are generic, such as image001.jpg, create a mapping sheet before renaming them. The mapping should show the old filename, product identifier, new filename, file type, and intended image role.

Do not assume that product content is the only information worth saving. Orders, customer records, tax details, and sales history may have separate export processes and permissions. Review sales data guidance before deciding what should be archived, migrated, or retained outside the new ecommerce platform.

Clean descriptions and image assets

Migration is an ideal time to make product copy consistent. Remove obsolete HTML, duplicated specifications, broken characters, and references to the old NCR storefront. Keep essential buying information near the beginning of the description, including dimensions, materials, compatibility, capacity, care instructions, warranty details, and what is included in the package.

Use a repeatable structure for every product category. A drinkware item might need a short benefit-led summary, a longer description, technical specifications, care guidance, and shipping notes. Content should be original and useful rather than a collection of search phrases. Include relevant terms such as product type, material, size, finish, color, and intended use where they accurately describe the item.

Standardize image files before uploading them. Use descriptive, lowercase filenames with hyphens, such as stainless-steel-cocktail-shaker.jpg. Check that images are sharp, properly cropped, and free of watermarks from the former platform. When reviewing stemware examples, for instance, distinguish between a primary product photo, a detail view, a lifestyle image, and a size or capacity graphic. Each should have meaningful alternative text that describes what is visible.

Match fields to the replacement platform

Magento and WooCommerce organize catalog data differently, even when they support similar products. Before importing anything, create a field-mapping document that connects each NCR field to its destination. Include title, SKU, slug, description, short description, categories, tags, attributes, variations, prices, tax class, stock quantity, image gallery, alt text, and metadata.

Pay special attention to variable products. A parent product may share descriptions and images with several child SKUs, while the new system may require separate variation records. Confirm how color, size, capacity, and finish are represented. A failed variation import can result in products that appear available but cannot be selected or purchased.

Decide which URLs should remain similar and which must change. If the structure changes, prepare permanent redirects from old product and category addresses to their closest new equivalents. Avoid sending every retired URL to the homepage; shoppers and search engines need a relevant destination.

Test the imported catalog

Import a small group of products before moving the entire catalog. Choose simple products, products with multiple variants, products with several images, and items containing custom attributes. This pilot exposes field-mapping problems while corrections are still manageable.

Inspect the product pages on desktop and mobile. Confirm that descriptions are readable, image galleries load in the right order, alt text is present, prices display correctly, and stock messages reflect the source system. Test filters, search results, category breadcrumbs, related products, and add-to-cart behavior. A product can look correct in the administration panel while displaying incorrectly to customers.

Use this quality-control checklist before approving the full import:

• Compare product counts, active statuses, and category totals between systems.
• Open representative products from every major category and variation type.
• Check image sharpness, cropping, filenames, alt text, and gallery order.
• Test search terms, filters, sorting, breadcrumbs, and internal product links.
• Review redirected URLs and record any missing or duplicate destinations.

Keep a list of exceptions instead of silently correcting records without documentation. An exception log makes it easier to repeat the process for future imports and shows which products require manual attention.

Launch with a controlled content switch

Schedule the final migration during a quiet sales period. Freeze catalog edits in NCR shortly before the final export so that new descriptions, images, prices, and inventory changes are not lost. If the store remains active during the transition, compare the final export with the pilot data and identify changes that need to be applied manually.

Before changing the domain or public links, complete a launch review. Confirm SSL protection, image permissions, checkout behavior, analytics, payment settings, tax configuration, and transactional email templates. Check that the replacement platform does not expose staging pages to search engines and that old URLs have the intended redirects.

After launch, monitor search coverage, page errors, image loading, product availability, and customer support messages. Compare traffic and conversion behavior with the previous period, but allow for normal fluctuations during the transition. Fix broken images and incorrect descriptions quickly because small catalog errors can affect both trust and revenue.

A successful migration leaves more than a copy of the old NCR catalog. It creates a cleaner product information system with organized assets, consistent descriptions, reliable category paths, and documented ownership of every important field. Begin with an audit, preserve the original exports, test in stages, and coordinate the final switch with your ecommerce partner so your product content can support the next platform from its first day.