Skip Navigation

Best practices for migrating to an enterprise organization

Consider the following recommendations when you plan your migration.
  • Rename any existing user attribute with the name “Organization” to avoid conflicts.
    BlackBerry AtHoc
    provides an enterprise user attribute with this name for targeting users by organization.
  • Plan the number of suborganizations and how they are organized.
    • Create a new enterprise organization rather than reuse a headquarters organization if there are existing users. Move the headquarters organization under the enterprise level.
    • Do not make the suborganizations too granular. For example, in a large corporation, create organizations by site, region, or division. Do not create an organization for each department or team.
  • Plan the promotion of attributes and alert folders. Content that is common among the existing organizations should be promoted.
    • Use enterprise attributes and alert folders to enforce consistency.
    • If more than one organization uses the same user attribute, the attribute should be promoted to the enterprise level.
    • If organizations use different values for the same user attribute being promoted, all values are promoted to the enterprise level.
    • Think about situations in which you need to alert the entire enterprise. What attributes do you need to target all users in an alert? These attributes should be promoted to the enterprise level.
    • Attributes that are for only one suborganization should stay at the suborganization level.
    • The “Emergency Community” and “Organization Hierarchy” attributes are not available for targeting in the enterprise organization.
  • Create all user accounts at the suborganization level, not at the enterprise level.
  • Authorized administrators can manage suborganization accounts from the enterprise organization.