Oracle ATG Web Commerce to Ecwid Migration - Step-by-Step Guide & Expert Services

Introduction

Replatforming your e-commerce store is a strategic move that can unlock new growth opportunities and streamline your operations. For merchants currently running on Oracle ATG Web Commerce, the transition to a modern, flexible platform like Ecwid offers significant advantages, including enhanced user experience, simplified management, and improved scalability. While Oracle ATG is a robust enterprise solution, moving to Ecwid can provide the agility and ease-of-use many businesses seek.

This comprehensive guide will walk you through the entire process of migrating your valuable store data from Oracle ATG Web Commerce to Ecwid. Given the enterprise nature of Oracle ATG, the migration will primarily involve exporting your data into CSV files and then importing it into Ecwid via a dedicated migration solution, ensuring a smooth and accurate data transfer.

Prerequisites for Migration

Before you begin the data transfer process, thorough preparation of both your source Oracle ATG Web Commerce store and your target Ecwid store is crucial to ensure a successful and seamless transition. Proper groundwork minimizes potential issues and safeguards data integrity.

Preparing Your Oracle ATG Web Commerce (Source) Store

• Data Export: Oracle ATG Web Commerce does not typically offer a direct API for third-party migration tools in the same way modern SaaS platforms do. Therefore, you will need to export your store data into CSV (Comma Separated Values) files. This includes essential entities such as products (with all their SKUs, variants, images, and descriptions), product categories, customer records, order history, and potentially customer reviews and CMS pages.
• Data Cleanup: Before exporting, take the opportunity to clean up your data. Remove outdated products, inactive customer accounts, or redundant information. This ensures you only migrate relevant, high-quality data to your new Ecwid store.
• Access Permissions: Ensure you have the necessary administrative access to your Oracle ATG Web Commerce environment to perform comprehensive data exports.

For more details on preparing your source store, refer to our guide: How to prepare Source store for migration?

Preparing Your Ecwid (Target) Store

• Create an Ecwid Account: If you haven't already, sign up for an Ecwid account and set up your basic store shell.
• Install the Cart2Cart Ecwid Migration App: To facilitate the data transfer, you will need to install the "Cart2Cart Ecwid Migration App". This app handles the complexities of API connections and data import into Ecwid.
• Obtain API Credentials: To connect your Ecwid store, you'll need specific API credentials. You will typically require your Store ID and an Access Token, which can be generated from your Ecwid control panel. Ensure these credentials have sufficient permissions for data import.
• HTTPS Requirement: Ecwid requires HTTPS for secure API communication. Verify that your Ecwid store is configured with SSL/TLS.

For guidance on setting up your target store, see: How to prepare Target store for migration?

Performing the Migration: A Step-by-Step Guide

This section outlines the process of migrating your store data using a dedicated migration wizard, step-by-step.

Step 1: Start Your Migration

Begin by navigating to the migration service platform. Here, you'll choose to start a new migration process. You can opt for a DIY approach using the wizard or request assistance from experts.

Step 2: Set Up Your Source Store (Oracle ATG via CSV)

Since Oracle ATG Web Commerce is an enterprise platform not directly listed for API connection, you will select "CsvToCart" as your source shopping cart type. This indicates that your data will be transferred from CSV files that you have exported from your Oracle ATG store.

You will then be prompted to upload your prepared CSV files containing products, categories, customers, and orders. Ensure your CSV files are formatted correctly to ensure accurate data parsing.

For more information on CSV migrations, visit: CSV.File Data Migration.

Step 3: Set Up Your Target Store (Ecwid)

Next, select "Ecwid" as your target shopping cart. To establish a secure connection, you will need to provide your Ecwid Store ID and the Access Token you obtained during the prerequisites stage.

Remember, the "Cart2Cart Ecwid Migration App" must be installed in your Ecwid store to enable this API connection and handle data transfer. Ecwid's API also has rate limits, which the migration tool will manage, but it's important to be aware for very large data sets.

Step 4: Select Data Entities for Transfer

This crucial step allows you to specify exactly which data entities you want to migrate from your Oracle ATG CSV files to your new Ecwid store. Common selections include:

• Products: This covers all product details, including SKUs, descriptions, images, pricing, and stock levels.
• Product Categories: Your store's organizational structure for products.
• Customers: Customer accounts, including basic information and addresses.
• Orders: Historical order data, essential for maintaining customer service records.
• Product Reviews: Valuable social proof that enhances product credibility.
• CMS Pages: Important informational content pages.
• Coupons: Existing discount codes and promotions.
• Blogs Posts: Your content marketing assets.

You can choose to migrate all entities or select them individually based on your business needs.

Step 5: Configure Data Mapping

Data mapping is vital for ensuring data consistency between your old Oracle ATG Web Commerce structure and your new Ecwid store. In this step, you will match corresponding fields between the source CSV data and the target Ecwid store. This typically involves:

• Customer Group Mapping: Aligning customer roles from your CSV to Ecwid's customer groups.
• Order Status Mapping: Matching order statuses (e.g., "Processing," "Shipped") from your Oracle ATG data to Ecwid's equivalents.

Careful mapping preserves data integrity and ensures that your customer data and order history remain accurate and usable in your new store.

Step 6: Choose Additional Migration Options

The migration wizard offers various additional options to tailor the data transfer to your specific requirements. Consider selecting:

• Clear Target Store Data: If you're starting fresh, this option will remove any existing data in your Ecwid store before the migration, ensuring a clean import. Learn more: Clear current data on Target store before migration option.
• Preserve Order IDs: This keeps your original order numbers intact, which can be crucial for accounting and customer service. Find out more: How Preserve IDs options can be used?
• Migrate SEO URLs & Create 301 Redirects: Essential for maintaining your search engine rankings and link equity. This option ensures that old Oracle ATG URLs are redirected to their new Ecwid counterparts, preventing broken links.
• Migrate Images in Product Descriptions: Ensures that all embedded product images are transferred correctly.

Step 7: Perform Full Migration

Before committing to the full migration, it's highly recommended to perform a free demo migration. This allows you to review a limited set of migrated data (e.g., 10-20 products, customers, and orders) to ensure everything transfers as expected.

Once satisfied, proceed with the full migration. This process can take some time depending on the volume of your data. Consider adding a Migration Insurance Service to your plan, which offers additional remigrations and priority support, providing peace of mind during this critical transition.

Post-Migration Steps

The migration doesn't end when the data transfer is complete. Several critical post-migration steps are essential to ensure your new Ecwid store is fully functional, optimized, and ready for customers.

• Verify Data Integrity: Thoroughly check all migrated data. Confirm that products (SKUs, variants, pricing, images) are accurate, customer accounts are accessible, order histories are correct, and all other selected entities have transferred without errors. This step is vital for maintaining data accuracy and a seamless user experience.
• Configure Storefront Design and Functionality: Customize your Ecwid store's theme to reflect your brand identity. Set up payment gateways, shipping methods, tax settings (Ecwid supports multi-tax), and any other third-party apps or integrations your business relies on.
• Implement 301 Redirects: If you didn't enable the automatic 301 redirect option during migration, it's crucial to manually set up 301 redirects for all your old Oracle ATG URLs to their new Ecwid counterparts. This is paramount for maintaining your existing SEO rankings, preserving link equity, and preventing broken links that can harm your search engine visibility.
• Update DNS Records: Once you are confident that your new Ecwid store is fully operational and tested, update your domain's DNS settings to point to your new Ecwid store. This will direct your customers to your new platform.
• Conduct Thorough Testing: Perform comprehensive testing of all store functionalities, including product browsing, adding to cart, checkout process, payment processing, customer login, and mobile responsiveness. Ensure that the user experience is flawless across all devices.
• Go Live and Monitor: Announce your new store and closely monitor its performance. Pay attention to website traffic, sales, and any customer feedback to quickly address potential issues.

For any new data that accumulates on your old Oracle ATG store after the initial export, consider utilizing a Recent Data Migration Service to transfer only the latest updates. Should you need to re-transfer data or refine your migration, the Cart2Cart Remigration Service is available.