FAQ
Magecore answers common questions about platform migration, assessment, costs, AI usage, TCO reduction, and engagement models for Adobe Commerce / Magento operations in Brazil.
Yes. Magecore operates as a consultancy and agency specialized in Adobe Commerce / Magento in Brazil. "Boutique" describes our delivery model — senior team, partners leading, fixed scope — not a different service category.
We offer precision assessments, zero-downtime progressive migration, and strategic roadmaps for e-commerce operations in Brazil.
Marcio Maciel is co-founder of Magecore, a Magento pioneer in Brazil, Meet Magento BR speaker (2012, 2013, and 2017), and winner of the MageHackathon Marketplace at Magento Imagine 2018 in Las Vegas.
Before founding Magecore, he worked at E-smart, B2W, BSeller, Digital Hub, and Webjump, and led enterprise projects for Hering, Sephora, Ambev, Danone, Nestlé, Havan, LG, Samsung, and Samsonite. Full profile on our About page.
Between 3 and 6 months, using the Strangler pattern and progressive migration, without stopping revenue during the process.
Duration depends on catalog size, integrations, and accumulated technical debt. Each migration wave is validated in production before the next.
It is an AI-assisted multidimensional diagnostic that identifies margin leaks and technical debt in Adobe Commerce / Magento operations, delivered in 1 to 3 weeks.
The deliverable includes a map of invisible costs, prioritized interventions with financial impact, and a clear recommendation: migrate, optimize, or keep the current platform.
The initial 30-minute conversation and pre-diagnostic with the three main areas of concern are free.
The full Precision Assessment is a fixed-scope project; investment varies by operation size and complexity and is presented after the initial conversation.
AI is internal infrastructure for diagnostics, predictive monitoring, and delivery acceleration — not a product sold to the client.
We use AI to cross-reference cost, code, and operations data in assessments, detect failure patterns in incidents, and reduce rework in migrations and roadmaps.
Yes, when the monolith limits margin, change velocity, or scalability, and migration ROI exceeds the cost of maintaining the status quo.
In some cases the assessment shows the platform is not the bottleneck; integrations and infrastructure respond better to optimization. The decision is based on numbers, not tech trends.
Every recommendation is tied to client P&L metrics: TCO, conversion, support tickets, LTV, or annual operational savings.
We define a baseline before the intervention, a measurement period (typically 12 months), and report documented results — the same criterion used in published case studies.
Yes. We operate across Adobe Commerce, Magento Open Source, and Mage-OS with the same diagnostic, migration, and roadmap methodology.
Mage-OS is a community-driven, upstream-compatible distribution of Magento Open Source, governed by a nonprofit association, that moves faster on performance and security patches. Distribution choice depends on licensing, integrations, feature fit, and long-term strategy, evaluated in the assessment.
There is no platform license fee for Mage-OS — the software itself is open source. Real TCO is still hosting, specialized labor, security patches, release QA, monitoring, and incident support. Removing the license line does not remove those P&L costs.
For mid-size operations that do not need Adobe-exclusive features, license savings can outweigh open-source sustainment cost; at small scale, engineering hours often consume the gain. The Adobe Commerce / Magento Open Source / Mage-OS comparison and a Precision Assessment project which scenario wins on your numbers.
Both run the same Magento 2 core. Adobe Commerce adds a commercial license, native B2B, Adobe Sensei AI, and a contractual support/SLA package. Mage-OS is the community-driven open-source distribution without that Adobe commercial stack — you keep the core and own continuity.
Because the core is shared, data and most extensions can move between them; the decision is licensing, feature fit, and sustainment capacity, not a one-way technical door. See the three-way comparison guide, then validate with an assessment when TCO is material.
Magento Open Source is Adobe's free base. Mage-OS is an upstream-compatible community distribution of that base: faster security patches, PHP 8.4 DI lazy-ghost loading, the M137 admin theme, Mage-OS Lab add-ons, and a Composer mirror without an Adobe account.
Know-how, themes, and most extensions carry over; only the latest Mage-OS branch is supported. When the question is which open-source line fits sustainment and projected TCO, the comparative guide and an assessment give the P&L answer.
Yes. From Magento Open Source 2.4.8+, migration typically takes around 30 minutes with the official Mage-OS script and is reversible. Coming from Adobe Commerce, you keep the Magento core path but lose Adobe-exclusive features (native B2B, Sensei, commercial SLA) that were in the license package.
Extensions and themes usually carry over because the distributions share the core; still validate integrations and feature gaps before cutover. For the full how-to (prerequisites, Open Source and Commerce paths, post-cutover checks), see the migrate to Mage-OS guide. The comparison guide frames the trade-offs; an assessment confirms whether switching beats upgrading on the current line.
Yes. Mage-OS is a mature, production-used Magento distribution; Mage-OS 3.0 (May 2026) builds on Magento Open Source 2.4.9. There is no Adobe commercial SLA in the package — continuity and incident response come from your team, partner, or hosting. Only the latest branch is supported.
Production readiness is about operations as much as the release: patch cadence, QA windows, and who owns security. If the open-source model fits scale and feature needs, the next step is projecting TCO versus Adobe Commerce or Magento Open Source in an assessment.
For migrations to modular architecture with observability, 25% to 50% reduction in infrastructure TCO over 12 months is a realistic target for mid-size operations.
The exact percentage depends on the starting point: operations with high reactive legacy costs tend toward the upper range; each case is quantified in the diagnostic.
We work with fixed scope per phase: Assessment (1–3 weeks), Engineering (3–6 months), and Sustainment/Roadmap (12 months).
We do not sell ad-hoc hours. Each phase has deliverables, timeline, and expected financial outcome defined before kickoff. Dedicated squad models are evaluated case by case after the assessment.
Magecore's core is Adobe Commerce / Magento and Mage-OS, where we have over a decade of expertise.
For other complex e-commerce platforms, we evaluate fit in the initial diagnostic. The methodology (P&L, AI, modular architecture) applies, but delivery depth is greatest in the ecosystem where we started.
Sustainment is the third phase of the Magecore methodology, with a 12-month horizon: governance with quarterly go/no-go checkpoints tied to financial KPIs, predictive dashboards, and a roadmap with explicit ROI per initiative.
Predictive dashboards surface deviations before they become incidents, and architectural evolution is planned with a prioritization framework based on financial impact. Every roadmap initiative has a financial return attached.
In a fixed-scope project, each phase has deliverables, timeline, and expected financial outcome defined before kickoff; in an hourly contract, you pay for time spent, with no tie to results. Magecore does not sell ad-hoc hours or hour banks.
We work with fixed scope per phase — Assessment (1–3 weeks), Engineering (3–6 months), and Sustainment/Roadmap (12 months) — with incentives aligned to the client's P&L results, not to hours worked.
Yes. On Adobe Commerce, extended support for 2.4.5 ends in August 2026; Magento Open Source has no equivalent extended tier, and 2.4.5 is already outside the full official patch cycle. Without an upgrade plan, security, PCI, and reactive-cost risk rise over time.
The most common path is not a platform migration: it is a controlled upgrade to the latest supported Adobe Commerce / Magento release (Cloud or on-premise), with a risk plan and P&L impact. Temporary containment only makes sense with an explicit deadline. An assessment maps the real state before you choose the path.
