Migrating from Xibo® for Android to BrightSign®, display by display

If you already run Xibo® and you're moving screens onto BrightSign® hardware, the thing to understand first is how little actually changes: your CMS doesn't. Layouts, media, campaigns, schedules, display groups and users all stay exactly where they are. A migration here is swapping the box behind the screen, not moving platforms.

That's true because a player is defined by the protocol it speaks, not the vendor that made it. XiPlay implements Xibo®'s XMDS protocol, so a BrightSign® player joins your existing CMS as an ordinary display alongside whatever you're running today.

You do not have to do this all at once

This is the part teams most often get wrong, by assuming an estate migration is an event. It isn't. It's per-display. Both player types can run against the same Xibo® CMS at the same time, indefinitely. So you can:

• ✓Convert one screen, and leave the rest alone for a month.
• ✓Convert the screens that hurt most first: the ones that keep going black, or the wall that won't stay in sync.
• ✓Convert on natural boundaries: a store refit, a hardware refresh cycle, a new site.
• ✓Stop halfway, if it isn't working out, with no rollback project.

The per-display procedure

1. 1 Prepare a card. Extract the XiPlay package and copy its contents onto a class-10+ SD card (16 GB or more), then insert it into the BrightSign® player. That's the whole installation: no flashing tool, and nothing is installed on the device itself.
2. 2 Point it at the same Xibo® CMS. Enter your existing CMS address and key on the player's configuration screen. It's the same server your current players talk to.
3. 3 Authorize the new display in Xibo®. It registers as a new display and waits, exactly as any new Xibo® display does. Authorize it in the CMS.
4. 4 Schedule content to it. Add it to the display groups the old screen belonged to. It now receives the same layouts and schedules.
5. 5 Claim and license it. Note the hardware MAC from the player's activation screen, claim it in the XiPlay portal, and assign a license. Every new device runs the full software free for 14 days first, so you can prove the screen before you pay for it.
6. 6 Retire the old display. Once the new one is playing correctly, remove the old display from its groups and decommission it in Xibo®.

What to watch for

• ✓Display groups, not individual schedules. If you schedule to groups (and you should), the swap is just group membership: add the new display, remove the old one. If you've scheduled directly to individual displays, this is a good moment to fix that.
• ✓Timezone per display. The player takes its clock and timezone from the CMS. If content plays at the wrong hour after the swap, check the timezone on the new display in Xibo®. It's almost always that.
• ✓Video walls are all-or-nothing. A sync group must be a single model family on a wired network. You cannot half-migrate a wall: convert all of its players together, or none.
• ✓Licensing follows the hardware. Licenses are keyed to the player's MAC, so plan one license per new player. If you later RMA a unit, unassign and reassign the licence in the portal. You don't buy it again.

What you gain, concretely

Being specific rather than promotional: fanless, diskless hardware built for continuous duty; a self-healing watchdog that recovers a frozen player without a site visit; offline-first playback so a network drop pauses the refresh rather than the screen; and access to hardware capabilities (genlock video walls, HDMI-In) that a consumer box physically doesn't have.

What you don't gain is a new CMS to learn. That's the point.