You don't hate digital signage. You hate your CMS: the clunky UI, the random outages, the features that have been "on the roadmap" since 2018.
- Don't panic-migrate. First figure out if the problem is your CMS or your training, workflows, and content chaos.
- Inventory everything: screens, players, content types, data feeds, user roles, and integrations.
- Design the new world, then choose tools. Define goals and architecture before falling in love with demos.
- Build clean, not identical. Use the migration to simplify channels, templates, and tags.
- Run old and new in parallel. Pilot, test, and migrate in waves with clear rollback plans.
- Finish with optimization, not "it works." Fix workflows, train users, watch analytics.
So you start to think: "We should switch digital signage software." Then the fear kicks in — black screens, broken playlists, angry stakeholders, and that one VP who will spot the single offline screen in a building of 300.
This guide shows you how to switch digital signage platforms without wrecking your network or pretending "everyone will be fine."
A lot of teams hit a wall and decide "we need to switch CMS." Sometimes that's true. Other times the honest answer is brutal: you never really learned how to use the system you already have.
The rollout was rushed, training was an afterthought, and the people running digital signage already have two or three other jobs. No one documented workflows. No one set clear ownership. The CMS became the scapegoat for a pile of process and resourcing problems.
That doesn't mean your software is perfect. It does mean you should be honest about whether a new platform will actually fix anything if you repeat the same patterns.
Do You Actually Need to Switch CMS?
Before you start Googling "digital signage CMS migration," ask one blunt question: Is our problem the software, or how we're using it?
- You never had formal product training
- Your content workflows are chaotic
- IT locked down access so hard no one can experiment
- No one owns strategy — everything is "random stuff on screens"
- Your vendor is stagnating or has been acquired and deprioritized
- Core features are missing — scheduling, tagging, data-driven content, permissions
- Uptime is unreliable and support is slow
- Licensing costs are climbing without equivalent value
If you're in that second column, keep going. You're in migration territory.
The 6 Phases of a Clean CMS Migration
Think of a digital signage software migration in 6 phases: Discovery, Design, Build, Test, Cutover, and Optimize.
The messy migrations are the ones that jump straight to phase 5 and treat everything else like optional homework.
Discovery — What Do You Actually Have?
You can't migrate what you don't understand. Discovery is where you get brutally honest about your current network.
Inventory your screens
- Total number of screens and where they are
- Player hardware: model and operating system
- Basic network details
- Special cases — video walls, LED, touch, kiosks
If you don't have this in a spreadsheet, create one. It becomes your single source of truth throughout the migration.
Understand your content
- Content types: images, videos, HTML5, data feeds, live TV, dashboards
- Playlists and channels: how many, and which screens they feed
- Rules and dynamic content: time of day, location, audience, data feeds
- Localization and regulatory content where needed
For each important playlist or channel, capture who owns it, how often it changes, and what approvals it needs.
Map your integrations
Digital signage rarely lives alone. Document your data sources (POS, inventory, CRM, HR, calendars), authentication and access control, monitoring tools, and any ad tech stack for retail media or DOOH.
Design — Decide What "Better" Looks Like
After discovery, it's tempting to rush straight into vendor demos. Slow down. First, define what "better" actually means for your team.
Clarify your goals
- Reduce time to publish new content from X days to Y hours
- Support Z locations and W new screens over the next 3 years
- Enable localized content that local teams can manage safely
- Integrate with specific systems so pricing, schedules, or messages stay in sync
- Improve uptime and monitoring
Each goal should tie back to a real business outcome — not just "cool feature we saw in a demo."
Define must-haves vs. nice-to-haves
Must-haves might include: stable and actively developed platform, strong user and role management, simple playlist/channel structure, solid scheduling and targeting, good monitoring and alerting, real training and support options, and clear API capabilities.
This list is what you hold vendors to. It also helps you avoid getting distracted by shiny, irrelevant features.
Decide your architecture
Are you staying cloud-first, going hybrid, or keeping any on-prem components? Consider network and security rules, regulatory requirements, local control needs, and how much IT wants to own vs. outsource.
A smart path is often: keep compatible existing players where possible, and plan a phased hardware refresh for edge cases and aging devices. Many CMS platforms support a range of devices including specialized media players and system-on-chip screens.
Build — Set Up Your New CMS the Right Way
Once you've picked your new platform, the real work begins. If you work with a consultant, this is where we get very picky on your behalf so you don't inherit the same chaos in a new system.
Build a clean content and channel structure
Do not copy your old mess into the new system. Instead:
- Design a simple, logical channel hierarchy
- Use clear naming conventions for playlists, channels, and assets
- Standardize tags for location, language, campaign, audience
- Define "global" vs. "local" content areas
Rebuild key layouts and templates
Bring over layouts for common use cases: lobby, menu boards, KPI dashboards, wayfinding, promotions. Use the migration as an excuse to improve weak layouts and weed out outdated visual clutter.
Recreate data-driven content
This is where many migrations fall down. For each data-driven element: confirm the data source, decide whether to reuse the same integration or rebuild it, recreate business rules in the new platform, and test edge cases — missing data, weird characters, timeouts.
Set up user roles and permissions
A CMS migration is the perfect time to stop sharing one admin login with 12 people. Define who can create, approve, schedule, publish, change layouts, see reporting, and who gets admin rights (keep this list short).
Test — Run Both Systems Side by Side
This is the "dual running" phase. It's not glamorous, but it's what protects you from black screens and surprise failures.
Set up a pilot group of screens
Pick a mix of high-visibility locations, lower-risk test locations, and different hardware types and network situations. Mirror the existing content strategy — same channel types, same playlists, same schedule patterns. Run old and new CMS in parallel and compare.
Test like a pessimist
Don't just see if it "basically works." Try to break it. Test schedule changes, emergency messages, network hiccups, device reboots, data feed failures, and the kind of user mistakes people make in real life.
Measure performance and stability
Watch player uptime, content refresh times, error logs, and time to fix issues. If the new platform isn't clearly more stable and easier to manage than the old one, pause. Better to adjust now than after you cut over hundreds of screens.
Cutover — When You Actually Switch Everything
Once dual running looks solid, it's time to plan your full migration. This is where people get nervous, so a clear plan helps a lot.
Plan your cutover in waves
Do not flip the entire network in one night unless you absolutely have to. Group screens by location, region, or business unit. Sequence more complex locations after simpler ones. Leave breathing room between waves.
For each wave, define: exact screens and locations, what content and channels they'll run, the migration window, who is on call, and a rollback plan if things go sideways.
Communicate with stakeholders
Tell people what's happening. Explain the goal in plain language, share timing and impact, tell them who to contact if they notice something wrong, and reassure them there's a rollback plan. Silence is where rumors and panic grow.
Execute and monitor
During each cutover wave: have IT, content owners, and your vendor aligned on a live channel. Watch monitoring dashboards closely. Validate visual quality on real screens, not just the CMS preview. If something major breaks and you can't fix it quickly, use your rollback plan.
Optimize — Don't Stop at "It Works"
A lot of teams treat "the screens didn't catch fire" as the endpoint. That's baseline, not success.
Review and simplify workflows
Ask your users: Is content creation faster? Is scheduling easier or still confusing? Are approvals smooth or bottlenecked? What's still painful? Then adjust workflows, training, documentation, and user roles accordingly.
Level up content and strategy
Now that the plumbing is sorted, tighten your content calendar, align messaging with campaigns and business priorities, improve creative quality, and use analytics to find dead spots and winning content. You migrated to move forward, not to stand still on a shinier platform.
Keep an eye on analytics
Use your new platform's reporting to track uptime, monitor proof of play, measure performance of key messages, and spot devices that misbehave. This is also your ammo when leadership asks "what did we get out of this migration?"
Common Migration Mistakes to Avoid
Letting your vendor "handle everything" without oversight
Vendors know their product, not your politics, people, and processes. They might rebuild your old chaos in a new UI, skip change management, or overpromise on timelines.
Migrating junk content
If a layout has been running untouched since 2016, you don't need to port it pixel-perfect. Use the migration as a content cleanup — archive outdated assets, kill underused channels, standardize design patterns.
Skipping training
"Everyone will figure it out" is not a strategy. Plan real training sessions. Record them. Build quick reference docs. Create a place for users to ask questions and share tips.
Ignoring programmatic and retail media needs
If you're running or planning an in-store retail media network, consider ad server and SSP integrations, campaign booking workflows, revenue reporting, and brand safety rules. Migrating without the ad side is how you end up redoing work 6 months later.
Where Specialized Help Actually Pays Off
Could you manage a digital signage CMS migration alone with internal resources? Sure. You also could cut your own hair before a big event.
Bringing in a specialist helps when you're not sure which platform to move to, need someone who has actually migrated off and onto multiple CMS platforms, want a neutral view not tied to selling one vendor, or need proper expertise evaluating leading platforms. If you are migrating to Navori QL, I offer dedicated setup, training, and optimization as a certified Navori consultant.
An experienced partner will run discovery in a structured way through a software audit & analysis, help with software & hardware selection, set up proper workflow design & training, handle content management and content creation & strategy, and provide hands-on project-based consulting to keep things on track.
- We know exactly what screens, players, content types, and integrations we have today
- We have clear goals for what the new CMS needs to achieve
- We have documented must-have requirements and nice-to-haves
- We have chosen an architecture that fits our IT and security reality
- We have a plan for content structure, roles, and permissions in the new system
- We will run old and new platforms side by side and test thoroughly
- Our cutover is planned in waves with clear rollback paths
- We have training and onboarding lined up for users
- We know who owns the system after migration — both technically and strategically
If you're missing more than a couple of those, you don't need to panic. You just need to slow down and treat your CMS migration like the serious project it is.
Jordan Feil is an independent digital signage consultant with 17 years of industry experience. He has worked as a product manager at Navori Labs, a technical account manager, and a global marketing director before founding JAF Digital Consulting. He works with operators, vendors, and integrators on strategy, software selection, network audits, and go-to-market. No commissions, no vendor relationships that shape what he recommends.