.. _delete-issues-and-purges:

Delete issues and purges
------------------------

:bdg-primary:`Cisco`


.. tip:: 

   :ref:`use-action-search-to-navigate-automate`



Overview 
..........

Whenever CUCM and CUCX data is synced into VOSS Automate, it assumes management
of the data and, as a result, that data would be deleted by any hierarchy delete
performed in VOSS Automate. These deletes can fail if your CUCM model dependencies don't reflect 
the additional data contained in existing, provisioned dial plans brought into VOSS Automate.



Preventing delete failures 
............................

There are two ways to prevent delete failures:

* (Provider deployments) Work with a Cisco System Integrator to update your HcsCucmWrapperCascadeDelPWF
  workflow to handle the dependencies in your existing dial plan.
* Perform a purge instead of a delete.

  Purging deletes all users, subscribers, phone, profiles, and devices from a
  brownfield customer's VOSS Automate while leaving these objects on the Unified CM
  and the Cisco Unity Connection.


Execute a purge 
...................

To execute a purge:

1. Log in as a Reseller administrator or higher.
2. Go to the **Data Sync** page.
3. From the hierarchy drop-downs, select the customer whose data you need to
   purge. If the data was created at the Site hierarchy, the purge only takes
   place at site level.
4. Click **HcsPurge-<IP address + fully qualified domain name + hostname>**.
5. From the **Sync Type** drop-down, choose **Purge Local Resources**. All other
   default values remain unchanged.
6. Click **Execute**.
7. Repeat steps 4-6 for the CUCM.
8. Verify that the instances and device models are deleted by checking Phones,
   Users, and Voicemail.
   
   .. note:: 

      Now you can attempt to migrate the customer into Automate 
      by executing HcsPull from the same menu for CUCM and Unity Connection, and then running the overbuild.