This migration plan is generated through automated code analysis using AI and pattern matching. Actual migration complexity, timeline, and effort may vary based on specific business requirements, customizations, and implementation details.
Estimates
The estimated timeline, effort hours, and team size are provided for planning purposes only. These estimates do not include costs, SI partner rates, or binding commitments. For detailed project planning and accurate cost estimates, please consult with an Adobe Commerce certified implementation partner.
Scope
The output is directional, not definitive — it is meant to inform discussion, not serve as a final migration plan
The assessment helps identify where customization exists, potential areas of complexity, and likely migration considerations
Any findings would still need to be validated by the customer or their partner
This is exploratory only and does not imply a commitment to ACCS or a specific migration path
💡 Optimize Your Migration Journey
Review Thoroughly
Take time to carefully review each module, customization, and integration identified in this report. Not everything needs to be migrated — this is an opportunity to modernize and simplify your commerce platform.
Check the Exchange Marketplace
Before rebuilding modules, search the Adobe Commerce Marketplace for pre-built apps that can replace custom functionality. Using marketplace apps can significantly reduce migration time and costs while providing vendor-supported, production-ready solutions. If you don't find what you need, contact your Adobe team to request missing apps — Adobe prioritizes marketplace development based on customer demand.
Declutter & Simplify
Remove unused modules, eliminate redundant customizations, and leverage native ACCS capabilities where possible. A leaner migration means faster delivery, lower costs, and a more maintainable platform. Every module you eliminate reduces complexity, shortens timelines, and decreases ongoing maintenance.
Migration Complexity
Complexity ScoreMigration ComplexityOverall migration complexity based on the number and severity of high-, medium-, and low-impact modules in your codebase.
High
17 low · 5 medium · 36 high-impact modules
Custom ModulesCustom Module RatioShare of modules that are not standard Magento core. A high ratio means more platform-specific code to audit before cutover.
98%
58 of 59 modules
Third-Party ModulesThird-Party ModulesModules sourced from composer packages outside of Magento core. These may require compatibility verification or replacement during migration.
0%
0 of 59 modules
Critical HooksCritical HooksPlugins, observers, and preferences flagged as high-risk — each is a potential breakage point when the platform changes.
57
plugins, observers & preferences
Highest-Impact Modules
These modules have the most complex customizations and require the most migration attention.
Migration Drivers
Migration DriversThe primary categories of customization that determine migration effort and risk. Address these first when sizing and planning.
Customization FootprintCustomization FootprintCustom modules may rely on Magento internals not present in ACCS. A high custom ratio means more code to audit and potentially rewrite.
58 of 59 are custom modules
98%
7 vendor extensions detected
Plugins & ObserversPlugins & ObserversPlugins intercept core method calls; observers react to events. 'Around' plugins and chain conflicts carry the highest migration risk.
Class PreferencesClass PreferencesPreferences replace core classes entirely — the most fragile Magento pattern. They break whenever the overridden class changes upstream.
Critical preferences detected90 preferences · 45 critical0 with conflicts
Data ModelData ModelCustom tables are low-risk. Core table modifications are harder to migrate. Critical EAV attributes may conflict with the platform schema.
IntegrationsIntegrationsCarrier and payment integrations calling external APIs require vendor coordination and add risk to the cutover window.
3 integrations detectedNo external APIs detected
Customization Breakdown
Metric
Count
Status
Total plugins
37
Baseline
Critical pluginsCritical PluginsAround-type plugins that target a Magento core class (Magento\* namespace). They wrap or fully replace the intercepted method call — the highest-risk plugin pattern because they can suppress core behaviour and are most likely to break when the platform changes.
7
Critical
Around pluginsAround PluginsAround plugins wrap both before and after a core method call, fully intercepting execution. They carry the highest migration risk and should be refactored to before/after plugins where possible.
7
Runtime risk
Chain conflictsChain ConflictsMultiple plugins intercepting the same method. Conflicts make execution order unpredictable and are a common source of production bugs after migration.
4
Conflicts
Metric
Count
Status
Total observers
37
Baseline
Critical observersCritical ObserversObservers listening to high-stakes business events such as order placement, checkout submission, and payment processing. These touch the most sensitive parts of the commerce flow and carry the highest migration risk.
5
Critical
High-frequency observersHigh-Frequency ObserversObservers firing on high-volume events (e.g. every page load or catalog request). These need performance testing on the target platform — they are a common cause of regressions.
3
Performance risk
Metric
Count
Status
Total preferences
90
Baseline
Critical preferencesCritical PreferencesPreferences that replace a Magento core class (Magento\* namespace). Because they completely substitute the original class, they break whenever the overridden class is changed or removed upstream — the most fragile Magento customisation pattern.
45
Critical
ConflictsPreference ConflictsMultiple preferences targeting the same core class. Only one can win, so the override order is fragile — conflicts must be resolved before migration.
0
None
Metric
Count
Status
Total tables
21
Baseline
Custom tablesCustom TablesNew database tables introduced by custom or vendor modules — identified by the vendor name prefix in the table name. These are low-risk to migrate unless they reference core Magento tables via foreign keys, which creates a dependency on the platform schema.
8
Custom
Core table modificationsCore Table ModificationsChanges to Magento's own database tables (e.g. adding columns to sales_order). These conflict with platform schema upgrades and require a dedicated data migration plan.
13
Core modified
Total EAV attributes
33
Baseline
Critical EAV attributesCritical EAV AttributesEAV attributes flagged as high-risk — typically those with non-standard types, unusual scopes, or names that overlap with platform-reserved attributes. Validate each before cutover.
13
Critical
Metric
Count
Status
Total integrations
3
Baseline
Carriers with external APICarriers with External APIShipping carrier implementations whose PHP code makes outbound HTTP calls — detected via cURL, Guzzle, SoapClient, or API credential patterns. These carriers depend on third-party rate or label APIs that must be re-verified and re-credentialed after platform cutover.
0
Contained
Payment methods with external APIPayment Methods with External APIPayment method implementations whose PHP code (including any Gateway/ subfolder) makes outbound HTTP calls or references API credentials. These integrations require vendor coordination during migration — a failed payment gateway on go-live is a critical incident.
0
Contained
Module Reports
Select a module from the list to view its migration impact, hook details, and recommended actions.
ImpactImpactOverall migration risk for this module, derived from its hook volume, extensibility patterns, and AI-identified risk factors. High-impact modules should be addressed first.
High
Hook SurfaceHook SurfaceTotal extensibility touchpoints — plugins intercept core method calls, preferences replace core classes, and observers react to events. A larger surface means more migration work and more potential regression points.
4 plugins · 8 preferences · 1 observers
External DepsExternal DependenciesWhether this module calls external APIs (payment gateways, carriers, third-party services). External dependencies require vendor coordination and add risk to the cutover window.
No
Schema ChangesSchema ChangesWhether this module modifies the database schema (custom tables, EAV attributes, index changes). Schema changes require a data migration plan separate from the code migration.
Unknown
Purpose
PurposeAI-generated summary of what this module does and the business capabilities it enables. Use this to decide whether to migrate, replace with a marketplace app, or remove entirely.
No purpose summary available.
Hooks & Extensibility
Hooks & ExtensibilityAll Magento extensibility patterns used by this module. Each plugin, preference, and observer is a potential breakage point on migration — expand each category to see the details.
mm_additional_info_quote_item_conversion
criticalhigh
Transfers 15 custom marketplace attributes from quote items to order items during checkout
Migration impactHigh
Recommended approachFor ACCS: Migrate to Adobe I/O Events webhook listening to order placement events; implement App Builder Runtime Action to enrich order items with custom attributes by querying product data and customer data via ACCS REST APIs; store enriched data in App Builder Files/database; trigger downstream processes (revenue calculation, developer notifications) via subsequent events; cannot use plugin pattern in ACCS
authentication
lowhigh
Applies standard Magento authentication plugin to custom History controller
Migration impactLow
Recommended approachFor ACCS: Implement authentication in App Builder using Adobe IMS (Identity Management Services); use OAuth 2.0 for customer authentication; validate JWT tokens in App Builder Runtime Actions; leverage Adobe Commerce customer tokens for API authentication; this is standard App Builder security pattern
authentication
lowhigh
Applies standard Magento authentication plugin to custom History controller
Migration impactLow
Recommended approachFor ACCS: Implement authentication in App Builder using Adobe IMS (Identity Management Services); use OAuth 2.0 for customer authentication; validate JWT tokens in App Builder Runtime Actions; leverage Adobe Commerce customer tokens for API authentication; this is standard App Builder security pattern
authentication
lowhigh
Applies standard Magento authentication plugin to custom History controller
Migration impactLow
Recommended approachFor ACCS: Implement authentication in App Builder using Adobe IMS (Identity Management Services); use OAuth 2.0 for customer authentication; validate JWT tokens in App Builder Runtime Actions; leverage Adobe Commerce customer tokens for API authentication; this is standard App Builder security pattern
For
AppStore\Sales\Api\SalesRepositoryInterface
Event
Name
Area
sales_quote_item_set_product
mm_set_additional_info
global
Migration Guidance
Migration GuidancePrioritized actions derived from this module's extensibility patterns. Must Do items are blocking; Should Do items reduce regression risk; Nice to Have items improve long-term maintainability.
Must Do
Preserve existing customization workflows to avoid data loss or broken checkout flows
Should Do
Validate all 4 plugin(s) against Commerce 2 extension points
Review 8 preference override(s) for compatibility with core class changes
Test 1 observer(s) for event name changes and dispatch frequency
Nice to Have
Refactor around-plugins to before/after where possible to reduce interceptor overhead
Reduce class overrides by adopting available extension attributes or plugins
Test Focus Areas
Admin configuration flows and panel rendering
Approval and order status transition flows
Report Reliability
This section shows how completely the AI analysis covered your codebase. Lower coverage means some modules may have incomplete recommendations.
Analysis run on Mar 31, 2026
Analysis Coverage
Analysis Coverage
78%
78%
45 of 58 modules fully analyzed13 module(s) skipped — no custom code detected.
No failures — all analyzed modules completed successfully.
Technical details about the pipeline run. Useful for troubleshooting with Adobe support.