Magento Upgrade Service
Based on 3,000+ reviews on: 
What Data Can Be Transferred During a Magento Upgrade
Our Magento upgrade service can transfer the following data to your new store. Use the tabs below to see which data fields can be migrated to the latest Magento version
-
Products
- Name, SKU, Short Description, Full Description, Status
- Manufacturer, Tax Class
- Price, Special Price
- Quantity, Manage Stock
- Meta Title, Meta Description
- Weight, Width, Height, Depth
- Product Tags
- Attributes (Name, Values)
- Downloadable Products (Files, Max Downloads, Expiration Date)
- Grouped Products (Associated Products)
- Variants (Name, SKU, Weight, Quantity, Manage Stock, Image, Price, Special Price)
- Thumbnail Image, Additional Images
Product Categories
- Name, Description
- Sort Order
- Image
- Meta Title, Meta Description
-
Customers
- First Name, Last Name, Email
- Billing Address
- Username, Password
- Status
- Created Date
- Display Name
-
Orders
- Order ID, Order Number
- Order Date, Order Status
- Order Items (Name, SKU, Option), Product Price, Quantity
- Sub Price, Discount Price, Tax Price, Shipping Price, Total Price
- Order Comments
- Customer Name, Email
- Billing Address (First Name, Last Name, Company, Address 1, Address 2, Country, State, City, Zip Code, Telephone)
- Shipping Address (First Name, Last Name, Company, Address 1, Address 2, Country, State, City, Zip Code, Telephone)
-
Manufacturers
- Name
-
Taxes
- Tax Class (Name)
- Tax Rate (Country, Rate)
-
Coupons
- Description
- Coupon Code, Coupon Date
- Customer Groups
- Uses Per Coupon, Uses Per Customer
- Discount Amount/Percent
- Coupon From Date, Coupon To Date
-
Reviews
- Created Date
- Status
- Rate
- User Name, User Email
- Comment
-
CMS Pages
- Title / Name
- Created Date
- URL
- Description
- Categories
- Thumbnail Image
Blogs
- Created Date
- URL
- Description
- Categories
- Thumbnail Image
Blog data is available only when the Magento store uses a supported blog extension or app.
-
Multiple Languages
- Products (Name, Description, Attribute)
- Categories (Name, Description)
- CMS Pages (Name, Description)
- Blogs (Name, Description)
*Available fields may vary depending on your Magento version, store configuration, and installed extensions.
See how your Magento data will look in the fresh target store. Start with a Free Demo or speak with a migration specialist about your project.
How LitExtension’s Magento Upgrade Service Works
LitExtension prepares a fresh Magento target store, maps the selected data, runs the migration, and validates the result. Your source store stays available during the main transfer.
We review your current Magento version, target release, data volume, store views, and custom fields, then confirm the entities and additional options included in the migration.
We prepare the fresh target Magento installation, connect both stores, and map products, categories, attributes, customers, orders, CMS content, and supported SEO fields to the correct target structures.
We migrate the selected data while the source store remains available, then compare entity totals and review key records and relationships. Recent Data Migration or Smart Update can capture eligible changes before launch.
Rebuild Magento on a Fresh, Current Installation
LitExtension’s Magento Upgrade Service is designed for merchants who want a clean Magento store on the latest supported version without carrying the old codebase into the new environment. We prepare a fresh Magento target installation and migrate the business data selected for the project.
Magento 2.4.9 is the current minor release. Your project can target Magento Open Source, Adobe Commerce, or another supported release selected for compatibility with your implementation plan.
This is a data-first, clean-store upgrade. It differs from an in-place version update that modifies the existing Magento codebase. LitExtension maps and transfers supported store data to a separate target, then validates the migrated records and their relationships.
Why choose a clean-store Magento upgrade?
1. Start with a clean Magento foundation
A fresh target installation avoids automatically carrying forward outdated core files, unused extensions, legacy configuration, or years of code-level changes. Your implementation team can decide what should be rebuilt, replaced, or retired around the migrated business data.
2. Preserve the data your business still needs
Rebuilding Magento does not mean starting from zero. Products, categories, customers, orders, attributes, CMS content, reviews, and supported SEO fields can be migrated to the new store according to the agreed scope.
LitExtension maps the relationships between entities so products remain assigned to categories, configurable products remain connected to variants, and orders remain associated with the correct customers where the source data supports those relationships.
3. Keep the source store available during migration
The main migration runs separately from your live storefront. Customers can continue browsing and placing orders on the source store while the selected data is transferred. Before launch, eligible new or updated records can be moved through Recent Data Migration or Smart Update. A short cutover window may still be required for final synchronization and verification.
4. Move only the records you want to retain
A clean-store rebuild creates an opportunity to leave unnecessary legacy records behind. The migration scope can be based on selected entity types, store views, custom mappings, and supported additional options rather than copying the entire old environment without review.
Magento 1 to Magento 2 and older Magento 2 to the latest version
Magento 1 to Magento 2: Magento 1 and Magento 2 use different architectures, so moving between them is a platform migration rather than a routine version update. LitExtension creates the new Magento 2 destination and transfers the supported catalog, customer, order, content, and SEO data required for the rebuild.
Older Magento 2 to Magento 2.4.9: If you do not want to update the existing codebase in place, LitExtension can migrate selected data into a fresh Magento 2.4.9 installation. This is especially useful when the current store is already due for a redesign, extension review, or broader rebuild.
Before selecting the target, review the official Magento Open Source 2.4.9 release notes or Adobe Commerce 2.4.9 release notes with the team responsible for your target-store implementation.
How LitExtension supports data continuity
- Field and entity mapping: Source records are mapped to the corresponding Magento 2 structures, with project-specific mapping available for supported custom data.
- Relationship validation: Entity totals, key records, and relationships are reviewed after migration.
- SEO data transfer: Supported URL keys, meta titles, meta descriptions, URL rewrites, and 301 redirects can be included to maintain URL continuity. Search rankings cannot be guaranteed.
- Historical order data: Orders and supported invoices, credit memos, and shipments can be migrated with their related customers and items.
- Store-view mapping: Languages, currencies, localized content, and store-view relationships can be mapped where supported.
- Post-migration updates: Eligible Re-Migration, Recent Data Migration, and Smart Update services help resolve migration issues or capture changes made before launch.
When is a clean-store Magento upgrade the right choice?
- You are moving from Magento 1 to Magento 2.
- Your Magento 2 store runs an older release and you prefer a fresh target installation.
- You are planning a redesign or wider Magento store rebuild.
- You want to review legacy extensions and customizations instead of carrying them forward automatically.
- You need to preserve products, customers, order history, content, and supported SEO data.
- You want the data migration separated from theme, extension, infrastructure, and deployment work.
This approach may not be the right fit if you need to keep the existing Magento codebase, theme, extensions, custom modules, and server configuration with minimal change. In that case, an in-place technical upgrade may be more appropriate. Review the FAQs below or chat with our team to confirm which approach matches your project.
Plan the migration and cutover
LitExtension first confirms the source and target versions, data volume, store views, selected entities, and required mappings. After the target is prepared, we run the migration and validate the result. Near launch, eligible recent or updated records can be synchronized before traffic moves to the new store.
Talk to a Magento migration specialist to review your current store, target version, and data scope.
Let our Magento migration specialists prepare the fresh target store, move the agreed data, and validate the result.
Data Security During Magento Upgrade
Server Security
Migration tasks run in controlled cloud environments with access limited to the systems and data required for the agreed project.
Data Security
Store connections and data transfers are protected in transit via HTTPS. Data handling and retention follow LitExtension’s Data Security Policy.
Data Access Restriction
Only authorized team members can access migration credentials and store data when required to deliver the agreed service.
GDPR Compliance
LitExtension is compliant with GDPR regulations, a global data protection law passed by the European Union.
Data Confidentiality
Credentials and store data are used only for the agreed migration work and handled according to LitExtension’s security and confidentiality policies.
Payment Security
Payments are processed by secure third-party payment providers. LitExtension does not store your full payment-card details.
Why Choose LitExtension for a Clean-Store Magento Upgrade
