TL;DR
- Do not 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. You cannot migrate what you do not understand.
- Design the new world, then choose tools. Define goals, architecture, and permissions before you fall in love with vendor demos.
- Build clean, not identical. Use the migration to simplify channels, templates, and tags instead of copying old problems into a new UI.
- Run old and new in parallel. Pilot, test, and migrate in waves with clear rollback plans so black screens never hit the public.
- Finish with optimization, not “it works.” Fix workflows, train users, watch analytics, and keep improving once the new CMS is live.
- Bring in help if needed. An independent specialist can keep vendors honest and stop you from becoming full time migration support.
You do not hate digital signage.
You hate your CMS:
Clunky UI
Random outages
“That feature is on the roadmap” since 2018
New content takes three approvals and a blood oath to publish
So you start to think: “We should switch digital signage softwares.”
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.”
The uncomfortable truth: it is not always the software
A lot of teams hit a wall and decide “we need to switch CMS.” Sometimes that is true. Other times the honest answer is brutal: you never really learned how to use the system you already have.
I see this all the time. 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 does not 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 rushed implementation, light training, and “who owns this, exactly” patterns. Sometimes the right move is to reset how you use your existing CMS before you go shopping for a new one.
First Thing: 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 are using it?
Once you admit it is not always the software, you can ask a sharper question: do we really need to switch CMS, or do we need to fix how we use the one we already have?
You might not need a full migration if:
You never had formal product training.
Your content workflows are chaotic.
IT locked down access so hard that no one can experiment.
No one owns strategy, so everything is “random stuff on screens.”
In that case, some consulting, better governance, and real training can squeeze a lot more value out of what you already have.
You probably do need to switch platforms if:
Your vendor is clearly stagnating or has been acquired and deprioritized
Core features are missing: granular scheduling, proper tagging, data driven content, user permissions
Uptime is unreliable and support is slow or unhelpful
You have outgrown the feature set and it is blocking real projects, not just “nice to have” ideas
Licensing costs are climbing without equivalent value
If you are in that second list, keep going. You are in migration territory.
Need Help Choosing the Right Cloud Signage Platform?
This guidance comes from someone who's been on both sides of the table—as a vendor helping organizations deploy cloud signage successfully (Navori Labs, X2O Media), and now as an independent consultant helping clients avoid expensive mistakes.
My job isn't to sell you a specific platform; it's to help you make the smartest decision for your organization's specific context. No sales pressure. No vendor kickbacks. Just honest guidance based on 16+ years of field experience.
Need help evaluating vendors, auditing your current setup, or building a realistic migration roadmap?
Big Picture: The 6 Phases of a Clean CMS Migration
Think of a digital signage software migration in 6 phases:
Discovery
Design
Build
Test
Cutover
Optimize
The messy migrations are the ones that jump straight to phase 5 and treat everything else like optional homework.
Let us walk through each phase in plain language.
Phase 1: Discovery – what do you actually have?
You cannot migrate what you do not understand. Discovery is where you get brutally honest about your current network.
1. Inventory your screens
Start here:
Total number of screens and where they are
Player hardware: model and operating system
Basic network details
Special cases like video walls, LED, touch, and kiosks
If you do not have this in a spreadsheet, create one. It will become your single source of truth throughout the migration.
2. Understand your content
Next, look at what is actually running on these things.
List out:
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.
3. Map your integrations
Digital signage rarely lives alone.
Document:
Data sources like POS, inventory, CRM, HR, and calendars
Authentication and access control
Monitoring tools watching player health
Any ad tech stack you use for retail media or DOOH
Write this down like you are explaining it to a smart stranger.
Book a free consultation today
Phase 2: Design – Decide What “Better” Looks Like
After discovery, it is tempting to rush straight into vendor demos. Slow down. First, define what “better” actually means for your team.
1. Clarify your goals
Make a short, sharp list:
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 system] so pricing, schedules or messages stay in sync
Add programmatic or retail media capabilities
Improve uptime and monitoring
Each goal should tie back to a real business outcome, not just “cool feature we saw in a demo.”
2. Define your must haves vs nice to haves
Classic exercise, but actually do it.
Must haves might include:
Stable, actively developed platform
Strong user and role management
Simple playlist and channel structure
Solid scheduling and targeting
Good monitoring and alerting
Real training and support options
Clear API and integration capabilities
Nice to haves might include:
- Flashy “nice to have” features that are hard to maintain
This list is what you hold vendors to. It also helps you avoid getting distracted by shiny, irrelevant features.
3. Decide your architecture
Important question: are you staying cloud first, going hybrid, or keeping any on prem components?
Factors to consider:
Regulatory requirements
Local control needs
How much IT wants to own vs outsource
This is also where you should start to think about players. Do you keep existing hardware or change it out during migration? A lot of CMS platforms support a range of devices, including specialized media players and system on chip screens. Others are more picky.
A smart path is often:
Keep compatible existing players where possible
Plan a phased hardware refresh for edge cases and aging devices
Phase 3: Build – Set Up Your New CMS the Right Way
Once you have picked your new digital signage platform, the real work begins.
If you work with a consultant like JAF Digital Consulting, this is where we get very picky on your behalf so you do not inherit the same chaos in a new system.
1. 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 things like location, language, campaign, audience
Define “global” vs “local” content areas
Decide what is controlled centrally, what runs everywhere, and where local teams get room to experiment. Your future self will thank you every time you search for anything.
2. Rebuild key layouts and templates
Bring over:
Layouts for common use cases: lobby, menu boards, KPI dashboards, wayfinding, promotions
Templates for recurring formats: safety messages, HR updates, weekly offers
Use the migration as an excuse to improve weak layouts and weed out outdated visual clutter.
3. Recreate data driven content
This is where many migrations fall down. Dynamic content is the delicate stuff.
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
Test edge cases: missing data, weird characters, timeouts
4. Set up user roles and permissions
Digital signage CMS migration is the perfect time to stop sharing one admin login with 12 people.
Define:
Who can create content
Who can approve content
Who can schedule and publish
Who can change layouts or channels
Who can see reporting and analytics
Who gets admin rights (keep this list short)
You want enough control to avoid chaos, but enough flexibility so people can actually do their jobs.
Phase 4: Test – Run Both Systems Side by Side
This is the “dual running” phase. It is not glamorous, but it is what protects you from black screens and surprise failures.
1. Set up a pilot group of screens
Pick a mix of:
High visibility locations
Lower risk test locations
Different hardware types and network situations
Mirror the existing content strategy:
Same channel types
Same playlists
Same schedule patterns
Run your old and new CMS in parallel and compare.
2. Test like a pessimist
Do not just see if it “basically works.” Try to break it.
Test: Test schedule changes, emergency messages, network hiccups, device reboots, data feed failures, and the kind of user mistakes people make in real life.
3. Measure performance and stability
Watch:
Player uptime
Content refresh times
Error logs
Time to fix issues
If the new platform is not clearly more stable and easier to manage than the old one, pause. Better to adjust now than after you cut over hundreds of screens.
Phase 5: Cutover – When You Actually Switch Everything
Once dual running looks solid, it is time to plan your full migration. This is where people get nervous, so a clear plan helps a lot.
1. Plan your cutover in waves
Do not flip the entire network in one night unless you absolutely have to.
Instead:
-
Group screens by location, region, or business unit
-
Sequence higher risk or more complex locations after simpler ones
-
Leave some breathing room between waves so you can learn and adjust
For each wave, define:
-
Exact screens and locations included
-
What content and channels they will run on the new CMS
-
The migration window and who is on call
-
A rollback plan if things go sideways
2. Communicate with stakeholders
Tell people what is happening.
At a minimum:
-
Explain the goal of the migration in plain language
-
Share the timing and impact for their location
-
Tell them who to contact if they notice something wrong
-
Reassure them that there is a rollback plan if needed
Silence is where rumors and panic grow.
3. Execute and monitor
During each cutover wave:
-
Have IT, content owners, and your vendor or consultant aligned on a call or at least a live chat channel
-
Watch your monitoring dashboards closely
-
Validate visual quality and content accuracy on real screens, not just in the CMS preview
-
Capture any issues along with how you fixed them
If something major breaks and you cannot fix it quickly, use your rollback plan. A short delay is better than public failure.
Phase 6: Optimize – DO NOT Stop at “it works”
A lot of teams treat “the screens did not catch fire” as the end point. That is baseline, not success.
After migration, you should:
1. Review and simplify workflows
Ask your users:
Is content creation faster
Is scheduling easier or still confusing
Are approvals smooth or bottlenecked
What is still painful
Then adjust:
Workflows
Training
Documentation
User roles
Do not be precious about a process that looked good on paper but is clearly annoying in real life.
2. Level up content and strategy
Now that the plumbing is sorted, it is a great moment to:
Tighten your content calendar
Align messaging with campaigns and business priorities
Improve creative quality and consistency
Use analytics to find dead spots and winning content
You migrated to move forward, not to stand still on a shinier platform.
3. Keep an eye on analytics
Use your new platform’s reporting to:
Track uptime
Monitor proof of play
Measure performance of key messages or campaigns
Spot locations or devices that misbehave more often
This is also your ammo when leadership asks “what did we get out of this migration, exactly?”
Common Migration Mistakes to Avoid
Let us save you from a few headaches.
1. 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, underestimate edge cases, or overpromise on timelines.
2. Migrating junk content
If a layout has been running untouched since 2016, you do not need to port it pixel perfect into your shiny new CMS.
Use the migration as a content clean up:
Archive outdated assets
Kill underused channels
Standardize design patterns
If you hate how your screens look now, copying them exactly is not an upgrade.
3. 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.
4. Ignoring programmatic and retail media needs
If you are running or planning an in store retail media network or any kind of DOOH monetization, you must consider:
Ad server and SSP integrations
Campaign booking workflows
Revenue reporting
Brand safety rules
Migrating your digital signage CMS without considering 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 like JAF Digital Consulting helps when:
You are not sure which platform to move to
You need someone who has actually migrated off and onto multiple CMS platforms
You want a neutral view that is not tied to selling one vendor
You need proper Navori expertise but also want to evaluate other leading platforms
An experienced partner will:
Run discovery and inventory in a structured way
Help you decide whether to optimize or migrate
Shortlist and evaluate platforms based on your real needs
Train your people so they are self sufficient, not dependent on an agency forever
You end up with a network that is easier to run, easier to grow, and actually supports what the business is trying to do.
Final checklist: Are You Ready to Migrate?
If you can honestly say “yes” to these, you are in good shape:
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 are missing more than a couple of those, you do not need to panic. You just need to slow down and treat your digital signage CMS migration like the serious project it is.
If you want help with the ugly parts like platform selection, migration planning, and rollout, that is exactly the kind of work JAF Digital Consulting lives in. You bring the screens and the goals. We help you switch platforms without wrecking your network.
FAQs
When should we migrate our digital signage CMS instead of fixing the old one?
Migrate when the platform itself is holding you back. If you are missing key features, dealing with poor uptime, weak support, or rising costs, it is usually time to switch. If your main problems are lack of training, messy workflows, or unclear ownership, fix those first before you go through a full CMS migration.
How long does a digital signage CMS migration usually take?
It depends on the size and complexity of your network. A well planned migration with discovery, dual running, and user training often takes a few weeks to a few months. If someone promises a complete weekend migration for a large network, treat that as a warning sign.
Can we reuse our existing digital signage players when we switch software?
Often yes. Many CMS platforms support a wide range of existing media players and system on chip screens as long as the operating system and firmware are supported. Audit every player by make, model, and OS so you know which devices you can keep and which ones should be replaced as part of a phased hardware refresh.
How do we avoid black screens during a CMS migration?
Run your old and new CMS side by side and migrate in waves. Start with a pilot group of screens, test schedules, data feeds, and emergency messages, then roll out in stages. Give each wave a clear rollback plan so you can revert quickly if something unexpected breaks.
Do we need a consultant to migrate our digital signage CMS?
You can handle a migration internally, but a specialist can reduce risk and guesswork. An experienced consultant helps you choose the right platform, design a clean content and channel structure, coordinate IT and vendors, and train your users. That support is most valuable if your network is large, business critical, or tied to revenue from advertising or retail media.