Contents
Overview
As part of Sherweb’s migration to ThreatDown OneView, the existing ThreatDown marketplace SKUs will be replaced with new billing SKUs. This change may affect partners who use a Sherweb PSA integration and currently synchronize ThreatDown billing data with their PSA. Sherweb will update eligible SKU mappings as part of the migration process to help minimize disruption.
Who Is Affected?
This article applies only to partners who:
Use a Sherweb PSA integration.
Synchronize ThreatDown billing information with their PSA.
Have existing ThreatDown products or services mapped in their PSA.
If you do not use a PSA integration, no action is required.
What's Changing?
The ThreatDown migration introduces new Sherweb billing SKUs that will replace the existing ThreatDown marketplace SKUs.
As part of the migration:
Sherweb will transition eligible existing mappings to the corresponding new SKUs.
New ThreatDown SKU references may appear on invoices.
New ThreatDown products may appear within your PSA integration.
Product names or invoice descriptions may be updated to align with ThreatDown OneView.
This migration does not affect your pricing, subscriptions, services, or protected endpoints. Only the billing SKUs used for invoicing and PSA synchronization are changing.
ThreatDown SKU Mapping Reference
The following table identifies the replacement SKU for each existing ThreatDown marketplace SKU. Partners using PSA integrations can use this reference when validating mappings after receiving their first invoice containing the new ThreatDown SKUs.
Products Not Migrating
The following legacy products do not have a replacement SKU as part of the ThreatDown OneView migration:
The activation offers listed above are not billable replacement products and will no longer be included on invoices. MDR Data Retention - 30 days is being discontinued by ThreatDown and will not transition to a new SKU.
What Do I Need to Do?
No action is required before the migration.
After you receive your first invoice containing the new ThreatDown SKUs, you may review your PSA integration to verify that:
ThreatDown products are mapped to the correct PSA products or services.
Charges are assigned to the correct contracts, agreements, or customers.
Quantities and billing information are synchronizing as expected.
No manual mapping adjustments are required.
If any products are unmapped or appearing incorrectly, update the affected mappings in your PSA or contact Sherweb support for assistance.
What Should I Expect?
Following the migration, you may notice:
New ThreatDown SKU references.
Updated product mappings.
Different product names or invoice line descriptions.
New products appearing within your PSA integration.
The migration does not change your ThreatDown pricing. It only replaces the underlying billing SKUs used for invoicing and PSA synchronization.
Frequently Asked Questions
Do I need to recreate my ThreatDown products in my PSA?
No. Sherweb will update eligible SKU mappings as part of the migration process. After the transition, you should simply verify that the new ThreatDown SKUs are associated with the correct products and services in your PSA.
Will my existing PSA mappings be deleted?
No. The SKU mapping process is designed to preserve existing synchronization relationships when a billing charge moves from an old SKU to its replacement SKU.
When should I validate my mappings?
Validate your mappings after your first invoice containing the new ThreatDown SKUs has been generated. This allows you to confirm that billing data is synchronizing correctly through your PSA integration.
What happens if a product becomes unmapped?
Review the product mapping within your PSA integration and map the new ThreatDown SKU to the appropriate product or service in your PSA. If you need assistance, contact Sherweb support.
Could products appear twice in my PSA?
The migration is designed to transition existing synchronization relationships to the replacement SKUs. However, partners should review their PSA after receiving their first invoice and report any duplicate, missing, or incorrectly mapped products.
Does this change affect partners who do not use a PSA integration?
No. This change only affects partners using a Sherweb PSA integration with ThreatDown billing data.
Getting Help
If you notice missing, duplicate, or incorrectly mapped ThreatDown products after the migration, contact Sherweb support and provide:
Your Sherweb partner name.
The affected customer organization.
The PSA platform you use.
The affected ThreatDown product or SKU.
A description of the issue, including screenshots if available.
Key Takeaway
No action is required before the migration. Once you receive your first invoice containing the new ThreatDown SKUs, review your PSA integration to confirm that mappings, quantities, contracts, and billing data are synchronizing correctly. Sherweb will migrate eligible SKU mappings as part of the transition to help minimize manual remapping.