There is no migration work for HVS to Sales Engagement; the rename happened at the product level. The pattern below covers cleanup of legacy HVS-named artifacts that linger in inherited orgs.
- Inventory HVS-named artifacts
Setup, Permission Sets, search HighVelocity. Setup, Tabs, search HVS. Note legacy artifacts: permission sets, page tabs, list views, custom field names. These continue working under the Sales Engagement product but use the old branding.
- Decide rename versus leave-alone
Renaming legacy permission sets is cosmetic and risk-free. Decide based on how much the legacy naming confuses new admins or hires. For orgs onboarding people who never knew HVS, rename. For stable teams that know the legacy names, leave-alone is fine.
- Rename legacy permission sets and tabs
Edit the permission set, change the label to SalesEngagementUser or similar. Edit page tabs similarly. The API name on permission sets cannot change after creation; if you need a clean API name, create new permission sets and reassign users.
- Update internal documentation
Replace HVS references in admin runbooks, training materials, and onboarding docs with Sales Engagement. Document the historical name on the first reference for context, then use Sales Engagement consistently.
- Brief the team on the naming
Confirm that the team knows HVS and Sales Engagement refer to the same product. New hires especially benefit from explicit naming context; experienced admins switch between names without confusion.
Continue working under the Sales Engagement product. Rename labels or leave alone based on team preference.
Legacy HVS tabs render correctly; rename for clarity or leave for backward compatibility with internal training.
Salesforce Help redirects HVS to Sales Engagement. Update internal docs to current canonical name.
Cannot rename after creation. Create new permission sets if a clean API name matters; reassign users.
- HVS and Sales Engagement are the same product. Treat them as synonyms; legacy configurations work under the renamed product.
- Permission set API names cannot rename. Cosmetic label changes are possible; structural rename requires recreation.
- Old AppExchange listings and blog posts use HVS terminology. Translate to Sales Engagement when consuming the content.
- The Salesforce Help search index biases toward Sales Engagement. Search for Sales Engagement, not HVS, when looking for current documentation.
- Customer-facing language matters. Refer to the product as Sales Engagement in customer conversations; HVS sounds dated to anyone post-2022.