.. _overbuild_steps: Overbuild Steps --------------- .. important:: System Integrator Support Recommended - For all Managed Services: Day 2 Overbuild Projects, we recommend support from a System Integrator. Provider and Reseller Administrators can follow these general steps to use the Overbuild tool: 1. Provision the business hierarchy. This can be done manually in VOSS Automate or by bulk load (see "Bulk Administration" topics and :ref:`perform_a_bulk_load`). #. Provision Cisco UC Applications, network device lists, and network device list references. Once UC Applications are configured, the sync from Cisco Unified Communications Manager will be scheduled and executed. See "Data Sync" topics. #. Choose the device pool and devices for the site on both the **Site Defaults > General** and **Overbuild Defaults** tabs. See :ref:`overbuild_site_defaults`. #. Choose **Run Overbuild** to move the imported UC Applications data into the site hierarchy that corresponds with the existing deployed site. See :ref:`run_overbuild`. * Users exposed under the **User Management** menu are moved to their associated phones if the **Users** check box is selected on the **Run Overbuild** tool. Users are moved to their phones if the phones have the user set as the OwnerUserID, if the **Users** check box is selected on the **Run Overbuild** tool. Note: The User's role is not changed when moving to Site. * Lines are moved and marked as in use in the Directory Number (DN) inventory if the **Lines** check box is selected on the **Run Overbuild** tool. A Site DN inventory is created. If the DN instance already exists, it is updated as in use. The DN inventory instance is created at the site level by default. This can be set to Customer in the SiteDefaultDoc before running OverBuild. Note: Adding Directory Number inventory at Customer level is only possible if the DialPlan in use is non SLC(Site Location) Based, or if no DialPlan is in use. #. Choose **Overview Tool** to verify the number of Unified Communications elements at the selected hierarchy and below. See :ref:`overview_tool`. #. Optionally, review the device model types listed with hierarchy in the Device Models or **Subscriber Management** menu. See :ref:`device_models`.