Interactive Assessment
Meraki Migration
Readiness Assessment
Answer 12 questions about your environment to get a scored readiness report with timeline estimates, risk factors, and specific next steps.
Step 1 of 4
0%
Environment Profile
Tell us about your Meraki environment
These details help us estimate complexity, timeline, and risk.
01
How many Meraki networks are in scope for migration?
1 – 50 networksSmall environment
51 – 200 networksMid-size environment
201 – 500 networksLarge environment
500+ networksEnterprise-scale
02
What type of migration are you planning?
Organization consolidationMerging multiple orgs into one
Organization splitDivesting or spinning off a division
GovCloud migrationCommercial → FedRAMP Moderate
Hardware refresh / EOL replacementReplacing end-of-life devices at scale
03
How many Meraki organizations are involved?
2 organizationsSimple source → destination
3 – 5 organizationsMulti-org consolidation
6+ organizationsComplex multi-org environment
Operational Readiness
How prepared is your team?
Readiness gaps are the #1 cause of migration delays.
04
Do you have a complete, current backup of all network configurations?
Yes — automated, tested, and currentBackup runs regularly and has been validated
Partial — some configs backed up via API/scriptsNot all networks or settings are captured
Manual only — screenshots or docsNo programmatic backup
No backup existsConfigurations are only in the dashboard
05
Do you have documentation of network dependencies?
Fully documentedTemplates, VPN tunnels, RADIUS, API integrations all mapped
Partially documentedSome dependencies known, others undocumented
Tribal knowledge onlyKey engineers know it, but it's not written down
Not documentedDependencies are unknown
06
Have you planned the license transfer strategy?
Yes — license plan confirmed with Cisco/partnerTransfer path, EA implications, and timeline documented
In progress — discussions startedWorking with partner but not finalized
Not yet addressedHaven't started license planning
Risk Assessment
What constraints affect your migration?
These factors determine how much risk mitigation your migration needs.
07
What is your tolerance for network downtime during migration?
Near-zero toleranceHealthcare, finance, 24/7 operations
Limited maintenance windowsWeekends or off-hours only
Flexible — we can schedule windowsBusiness can accommodate planned downtime
08
Are there compliance or regulatory requirements affecting the migration?
Yes — PCI, HIPAA, CMMC, or similarCompliance baseline must be maintained throughout
SOC 2 or general IT governanceChange management documentation required
No specific compliance requirementsInternal standards only
09
Do you have on-site IT staff at each location?
Yes — IT staff at all or most sitesPhysical device access available
Some sites — hub-and-spoke modelRegional IT covers multiple sites
No — all remote / no on-site ITEntirely cloud-managed, no local hands
Timeline & Resources
What's driving your migration timeline?
Understanding urgency and resources helps us calibrate the assessment.
10
What is your target completion timeline?
Under 4 weeksUrgent — regulatory or contractual deadline
1 – 3 monthsStandard planning cycle
3 – 6 monthsWe can plan methodically
Just exploring — no hard deadlineScoping phase
11
How experienced is your team with Meraki API / automation?
Advanced — we build with the Meraki API regularlyComfortable with scripted operations
Some experience — we've used the APIBasic scripting capability
None — dashboard onlyNo API or automation experience
12
Have you done a Meraki migration before?
Yes — at this scale or largerWe know the process
Yes — but smaller scaleMoved a few networks before
No — first migrationThis is new territory for our team
0
/ 36
Category Breakdown
Estimated Timeline
Recommended Next Steps
Ready to scope your migration?
Boundless has executed 200+ Meraki migrations. We can validate this assessment, identify hidden risks, and build your migration runbook in a single scoping call.
Book a Migration Scoping Call
Built by Boundless · Cisco ecosystem software for network operations