How to create a backup of your entire NCR Retail Online site

Creating a backup of your entire NCR Retail Online site requires more than downloading a product catalog. A dependable archive should preserve the store’s content, customer and order records, product data, images, search-engine settings, configuration details, and any information needed to rebuild the operation elsewhere.

This process is especially important because NCR Retail Online has been discontinued. Depending on your account status and partner arrangement, some administrative features may no longer be available. Start by confirming what access remains and whether your NCR Counterpoint partner can provide an export, database copy, or assisted transition.

A backup is also different from a migration. A migration transforms information for a new platform such as Magento or WooCommerce, while a backup preserves the original state as evidence and as a recovery resource. Keeping both gives your business a safer path through the change.

Define what the archive must contain

Begin with an inventory of every part of the online store. Include product titles, descriptions, SKUs, prices, cost information, stock quantities, categories, variants, manufacturer details, tax settings, shipping rules, discount codes, and product relationships. If the system supports custom fields, record those as well, since they can be overlooked during a basic catalog export.

Customer and transaction data deserve separate attention. Determine whether you are permitted to retain personally identifiable information, payment-related records, tax documents, and order histories under your company policies and applicable privacy regulations. Never store full payment card data unless your compliance procedures explicitly allow it and the data is handled through an approved secure system.

The archive should also cover the storefront itself. Save page content, navigation menus, URL structures, redirects, blog posts, downloadable files, email templates, promotional banners, and store policies. Record integrations with payment gateways, shipping providers, accounting software, marketplaces, analytics tools, and inventory systems without exposing secret keys in an unprotected document.

Prepare access and document the store

Use an administrator account with the smallest permissions needed for the work. Before exporting anything, verify that you can access the product area, order history, customer records, media library, settings, and any available reporting or data-export tools. If a section is inaccessible, note the limitation immediately rather than assuming it is included in another file.

Create a simple inventory document containing the store name, account identifiers, export dates, time zone, currency, active domains, connected services, and the people responsible for approval. Screenshots can help preserve settings that cannot be exported, but they should supplement structured files rather than replace them.

If NCR Retail Online access has already been restricted, contact the NCR Counterpoint partner that managed the store. Ask specifically what can be exported, whether a database-level backup exists, how media files can be retrieved, and how long the information will remain available. Keep a written record of requests and responses for future reference.

Export the data in a controlled order

Perform exports in a consistent sequence so that relationships between records remain clear. A useful order is configuration, catalog, customers, orders, content, and media. Run the exports during a quiet trading period where possible, then record the exact date and time so the archive can be compared with later reports.

Use native export tools when available and preserve the original file format. CSV, XML, JSON, SQL, PDF, and image files can serve different purposes, so do not convert everything into a single spreadsheet. Keep an untouched “source” copy and create separate working copies for cleaning or importing into a replacement store.

The following structure helps distinguish essential records from supporting material:

After each export, open a sample of the files. Check that accented characters, leading zeros in SKUs, decimal prices, dates, and variant relationships have not been changed by spreadsheet software. A file that downloads successfully can still be incomplete or damaged.

Capture files, media, and search settings

Media files are frequently missed because they may be stored separately from catalog data. Download original product photographs, category images, logos, PDFs, manuals, videos, and promotional graphics. Preserve directory names and filenames where possible, then create a media index that connects each asset to its product, page, or campaign.

Save the current URL map as well. Include product, category, informational, blog, and account URLs, along with canonical tags, robots directives, XML sitemap locations, structured data notes, and active redirects. These details can affect organic traffic after the store is shut down or moved.

Search metadata needs a dedicated export because it may not appear in a standard product file. Titles, meta descriptions, image alternative text, heading structures, and indexation rules should be recorded separately. When preparing the next store, this guide to migrating SEO metadata can help preserve important search fields instead of treating them as optional content.

Verify completeness before storing the archive

Verification should compare the backup with the live store or with authoritative business reports. Count products, active variants, categories, customers, orders, pages, media files, and redirects. Compare revenue totals and order counts for selected periods, and investigate any mismatch rather than adjusting figures manually.

Open representative records from every major data set. Check a simple product, a product with variants, a discontinued item, a customer record, a completed order, a refunded order, a page with embedded images, and a file download. This sample-based review often reveals missing images, broken relationships, truncated descriptions, or incorrect date formats.

Calculate checksums for important files if your team has the tools to do so. A checksum creates a repeatable fingerprint, making it easier to prove that an archive has not changed during transfer. Keep a manifest listing filenames, sizes, export dates, formats, and checksum values.

Protect sensitive information and preserve usability

Treat the backup as confidential business data. Encrypt the archive before transferring it, use a restricted storage location, and apply multi-factor authentication to the account that holds it. Avoid sending customer exports through ordinary email or leaving them on a personal computer without disk encryption.

Maintain at least two secure copies in separate locations, preferably using different storage systems. One copy can be retained for immediate migration work while another remains untouched as a reference. Define a retention period for customer and order information based on legal, accounting, and privacy requirements.

Separate credentials from the main archive. Document the names of connected services and the purpose of each integration, but store API keys, passwords, and private certificates in an approved secrets manager. Revoke obsolete credentials after the store has been decommissioned or migrated.

Use a practical backup checklist

A final checklist makes the archive easier for another employee, auditor, or migration partner to use. Each item should have an owner and a completion date, with exceptions documented rather than silently ignored.

• Export the catalog, customers, orders, content, settings, and media files.
• Record URL structures, SEO metadata, redirects, analytics, and integrations.
• Compare export totals with store reports and inspect representative records.
• Encrypt the archive, restrict access, and store copies in separate locations.
• Create a manifest with filenames, formats, dates, sizes, and verification notes.

Keep the checklist with the archive, not only in a project-management system. A future user should be able to understand what was captured, what could not be accessed, and which files are safe for import.

Turn the archive into a migration resource

Once the backup has been verified, use a copy—not the untouched master—as the working source for Magento, WooCommerce, or another replacement platform. Clean duplicate products, standardize attributes, map categories, and decide which historical records need to be imported. Retain the original values in case a transformation needs to be reversed.

Preserving search visibility requires an additional review of redirects, canonical URLs, metadata, internal links, and indexed pages. The guidance on protecting SEO rankings is useful when translating the archived URL structure into a WooCommerce implementation.

Before switching domains or DNS, test the new store with a limited data set and compare it against the archive. Confirm product availability, taxes, shipping calculations, checkout behavior, order history access, customer communications, and analytics tracking. When the evidence is complete and the replacement site is ready, ask your NCR Counterpoint partner or migration specialist to review the archive and execute the transition using the verified copy.