Import Broadsign Creator Content

This section describes how to migrate from Broadsign Creator to Broadsign Publish.

If you are currently using Broadsign Creator, you can request to be migrated to Broadsign Publish.

Note: During the migration, the messages will continue to play on your players.

Migration involves the following:

There are two possible migration paths:

  • Everything is imported from Broadsign Creator to Broadsign Publish and all users start using Broadsign Publish at the same time.
  • Everything is imported from Broadsign Creator to Broadsign Publish, but not all users start using Broadsign Publish. This allows you to manage user expectations and maybe train your users.

Note: If you choose the second migration path, an import is done for each group of users who will start working in Broadsign Publish. This import is a diff with what has changed in Broadsign Creator since the previous import to Broadsign Publish.

Note: Even if the data is imported, the users do not know the address and the new password for the Broadsign Publish server. They also do not know which screens are still pointing to Broadsign Creator, so they have not yet migrated to Broadsign Publish.

This section describes the steps required when migrating from Broadsign Creator to Broadsign Publish.

Broadsign suggests that you start by performing a migration in a sandbox environment.

Note: Everything that is done in the sandbox environment is for testing purposes only. The real migration will take place in the production environment.

To migrate to a Sandbox environment:

  1. Contact Broadsign Services to request the migration.
  2. As an initial import step, Broadsign Services syncs the database from Broadsign Creator to Broadsign Publish. The database includes the following information:
    • Content
    • Messages
    • Users
  3. Once the migration is done, Broadsign Services contacts you, requesting that you verify the migration result.
  4. If you want, you can modify the players configurations so that they point to the Broadsign Publish server instead of Broadsign Creator. See Configure Broadsign Publish in Broadsign Control for more details.

    Note: Broadsign Services suggests to start the migration with about 20% of the players that will be migrating. It will be easier to manage and make sure that everything works smoothly. You may also use this step to train some of your users.

    Note: The messages will continue to play on the players as if nothing happened and everything will be ready to be used in Broadsign Publish.

This section describes the steps required when migrating from Broadsign Creator to Broadsign Publish in a production environment.

Once you are satisfied with the sandbox migration, the real migration can proceed.

To migrate to a Production environment:

  1. Broadsign Services performs the database import as described in the sandbox procedure.
  2. As a subsequent import step, the players configurations must be modified so that they point to the Broadsign Publish server instead of Broadsign Creator. See Configure Broadsign Publish in Broadsign Control for more details.

    3. Note: Broadsign Services suggests to start the migration with about 20% of the players that will be migrating. It will be easier to manage and make sure that everything works smoothly. You may also use this step to train some of your users.

    Note: The messages will continue to play on the players as if nothing happened and everything will be ready to be used in Broadsign Publish.

  3. Second migration path: Repeat Step 2 for your other players, until you have migrated all of them. You must contact Broadsign Services to request the migration of the relevant users.

    4. An import is performed each time you sync new players to Broadsign Publish. This import is a diff with what has changed in Broadsign Creator since the previous import to Broadsign Publish.

  4. Communicate with the users of the migrated screens and give them the new URL address to use. It is expected that the users to migrate will not be using Broadsign Creator at the same time.

    5. Note: Broadsign Services does not remove access to Broadsign Creator. Broadsign suggests that you remove the access to make sure that your users no longer work in Broadsign Creator.

Your players must be configured so that Broadsign Publish can grab content from Broadsign Control. For any players that you wish to run content, they must be on a player configuration that has the Broadsign Publish Integration enabled.

For more details, see Configure Broadsign Publish in Broadsign Control.

  • If you run a version of Broadsign Control Player that is older than v13.x, Broadsign Services modifies the players configurations in Broadsign Control.

    • Note: Broadsign suggests to upgrade to the latest version of Broadsign Control Player.

  • If you run Broadsign Control Player v13.x or more, you can modify the players configurations yourself in Broadsign Control. For more information, see Configure the Player. If you prefer, you can still ask Broadsign Services to do the modifications for you.

If you are using Flash content in your Broadsign Creator messages, be aware that Broadsign Publish does not support Flash.

This content is listed in the Your Messages page with the Discontinued Icon icon as discontinued content.

The messages containing Flash content will continue to play on your players. The users will be invited to change the discontinued content or replace the message. For more information on how to modify messages, see Message Creation Tutorial.