--- title: "Migrate from Legacy Call Blocking" slug: "migrate-from-legacy-call-blocking" description: "Learn how to migrate from legacy call blocking to the 8x8 Call Blocking application, including exporting and importing blocked numbers seamlessly." status: "new" updated: 2026-09-15T20:48:20Z published: 2026-09-15T20:48:20Z canonical: "help.8x8.com/migrate-from-legacy-call-blocking" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.8x8.com/llms.txt > Use this file to discover all available pages before exploring further. # Migrate from Legacy Call Blocking ### Migrating from legacy call blocking If you are migrating from a legacy (custom) call blocking solution, you are most likely blocking numbers today using a custom field in your 8x8 Contact Center (VCC) local CRM — for example, a "Blocked Number" field and an "Is Blocked" flag checked by a custom script8 script. This article explains how to tell whether you can move to the standard 8x8 Call Blocking application yourself, and how to export your existing blocked numbers and import them if so. ### Applies to - 8x8 Contact Center: Admins - Customers with an existing custom (legacy) call blocking solution built on the VCC CRM - 8x8 Geo Routing & Call Blocking portal ### Step 1: Confirm you can migrate yourself Before you migrate, confirm whether your legacy call blocking solution has any additional features or use cases beyond blocking a number — or whether everything it does falls under the standard Call Blocking application's offering (block a number, per PBX/tenant or across all of them, with an optional reason, Inbound/Outbound/Both direction). - **If your requirements fit the standard offering:** you can migrate yourself. Export your existing blocked numbers from the VCC CRM, import them into the Call Blocking application, then contact 8x8 for a simple, free removal of your old customization so the new Call Blocking application takes its place. - **If it doesn't:** for example, your legacy solution blocks based on additional criteria, integrates with another system, or otherwise does more than block a number — you will need to work with 8x8 Professional Services to combine your existing customization with the standard Call Blocking application. > **Note** > If you have a custom script8 script built by Professional Services, enabling the standard Call Blocking application on top of it will produce an error. If that happens, talk to your account executive or account manager — Professional Services will need to combine the two for you. ### Step 2: Export your blocked numbers from VCC Use a Contact Center report to export the numbers your legacy solution currently blocks. 1. Go to the **Contact Center Agent Workspace**. 2. Click the **Customers** icon. 3. Click **Report** at the top right. 4. Click **New Report**. 5. Check the fields you need. You will typically need two: the field that stores the phone number, and the field that stores whether it's blocked. - The phone number is often in a custom field named something like **Blocked Number**, or under the out-of-the-box **Voice** field. - The "is blocked" indicator is usually a custom field that stores a value like **Yes**, **No**, or **N/A**. 6. Filter the "is blocked" field to **contains** or **equals**, and set the value to **Yes** (this can vary depending on how your solution is set up). 7. Click **Run**. > **Tip** > Copy and paste the report results directly into a spreadsheet (for example, Google Sheets or Excel). You can also click **Download**, but the report only downloads as HTML — you cannot export directly to a spreadsheet format. If you download it, open the HTML file and copy its contents into your spreadsheet instead. ### Step 3: Reshape and import your numbers into Call Blocking The Call Blocking application imports a CSV in a specific format, so you'll need to reshape your exported report before importing it. 1. In your spreadsheet, keep only the rows where the "is blocked" field is **Yes** (if your report filter didn't already narrow this down). 2. Arrange the data into three columns, in this order: **tenantOrPbx**, **phoneNumber**, **direction**. 3. Fill in **tenantOrPbx** with your tenant name for every row (your legacy solution's report won't include this column, since it only ever applied to one tenant). 4. Make sure every **phoneNumber** includes the country code (for example, **14085551234**, not **4085551234**). 5. **direction** is optional — Contact Center tenant entries are always Inbound, so you can leave this column blank or set it to **Inbound**. 6. Save the sheet as a CSV file. Your finished CSV should look like this: ``` tenantOrPbx,phoneNumber,direction my-tenant,14085551234,Inbound my-tenant,966512345678,Inbound ``` 7. In the Call Blocking application, select your tenant from the list on the left. 8. Click **Bulk upload** and select your CSV file. 9. Review the preview, which shows how many rows are valid and invalid, then confirm the import. ### Step 4: Remove your old customization Once you've confirmed your imported numbers are blocking calls correctly, contact 8x8 to request removal of your old call blocking customization. This is a simple, free request — 8x8 will remove the legacy customization now that the standard Call Blocking application has taken its place. ### Migrating from legacy call blocking: frequently asked questions **Q: How do I know if I can migrate myself?** A: If everything your legacy solution does is block a phone number from reaching your tenant — nothing more — you can migrate yourself. If it does anything beyond that (additional conditions, integrations, or other custom logic), you'll need Professional Services to combine it with the standard Call Blocking application. **Q: I got an error after trying to enable Call Blocking. Why?** A: This usually means you have a custom script8 script built by Professional Services that conflicts with the standard Call Blocking application. Contact your account executive or account manager — Professional Services will need to combine the two. **Q: What format does the import file need to be in?** A: A CSV with the columns **tenantOrPbx, phoneNumber, direction**, in that order. Phone numbers must include the country code. The direction column is optional for tenant entries, since they're always Inbound. **Q: When should I remove my old customization?** A: Only after you've confirmed your imported numbers are working correctly in the standard Call Blocking application. Removing the old customization first would leave you without call blocking in between. ## Related - [Getting Started with 8x8 Call Blocking](/getting-started-with-8x8-call-blocking.md)