Handover checklist
Magento Agency Handover Checklist
Use this checklist before switching Magento agency, reviewing support quality, or asking a new senior technical partner to take responsibility for a live store.
30-minute call | senior technical lead | no sales handoff
Fit
Who this is for
- Merchants reviewing whether their current Magento agency or support provider is still the right fit
- Teams leaving an agency and needing a clean transfer of access, code, infrastructure, and operational knowledge
- Commercial and technical owners who need to reduce risk before a support retainer, audit, or rescue engagement starts
Signals
Warning signs
- Deployment steps, rollback plans, or release notes are missing or only held by the outgoing agency
- Hosting, Magento Admin, Git, extension licences, or integration credentials are not clearly owned by the merchant
- Recurring incidents are being patched quickly but not documented, prioritised, or fixed at root cause
Checklist
Practical checks to work through
Request Magento Admin, Git repository, deployment, hosting, DNS, CDN, payment, analytics, monitoring, and backup access
Confirm who owns the codebase, Composer repository access, CI/CD pipeline, deployment scripts, staging environment, and rollback process
Review hosting stack, PHP version, database version, Redis/Varnish setup, queue workers, cron health, backup retention, and log access
List installed extensions, custom modules, licence owners, renewal dates, abandoned packages, and known compatibility issues
Document ERP, WMS, PIM, middleware, payment, shipping, email, and API integrations, including credentials and failure ownership
Review marketplace and M2E ownership: listing templates, stock sync rules, order routing, failed queues, and Prime/SFP responsibilities
Confirm security patch status, current Magento version, pending upgrades, known vulnerabilities, admin users, and 2FA coverage
Agree what the new support partner will own first: urgent risks, backlog review, release process, patching, monitoring, or rescue triage
Target state
What good looks like
- The merchant controls critical access, licences, credentials, and production decision-making
- Deployment, rollback, hosting, integration, and marketplace ownership are documented before support changes hands
- The incoming technical partner can review risk without guessing how the store is built or operated
Watch-outs
Common risks
- Changing support provider before confirming access to hosting, Git, backups, deployment, and key third-party accounts
- Assuming extension licences, middleware credentials, or marketplace configuration are transferable without checking ownership
- Treating the handover as an admin task when unresolved technical debt may require audit or rescue work first
Escalate
When to ask for senior help
- The outgoing agency cannot provide complete access, release notes, or deployment documentation
- You suspect checkout, ERP, marketplace, hosting, or security risk is hidden inside the handover
- You need a senior Magento engineer to review whether the next step should be audit, rescue, or retained support
Senior Magento review
Need a senior engineer to review the risk?
Share the blocker, affected area, urgency, and any useful logs or screenshots. We will help you identify the safest next step.
30-minute call | senior technical lead | no sales handoff