Mainly we would like to understand if we can use one of our sandboxes for that are we have to use some special trial sandbox for this. Main purpose is to do some early tests what functionality is supported and what are potential problems so we can estimate the amount of work more precisely and plan in the next year's budget. Would be thankful for any information on this topic =)
Hi Krisjanis,
For a Vlocity/Communications Cloud migration POC, I would first confirm the specific Salesforce product/version and migration path applicable to your org, since the available migration tooling and supported approach can vary.
For the POC, a sandbox can be useful for testing, but I would avoid assuming that an existing sandbox can simply be converted to the target Communications Cloud setup. Check with your Salesforce Account Executive/Architect or Salesforce Support about the supported sandbox/trial provisioning options for your org.
For early assessment, I'd focus on:
- Which Vlocity/Industries packages and features you currently use.
- Data model and customizations that depend on Vlocity objects.
- OmniStudio components, integrations, and custom Apex/LWC.
- Product Catalog/CPQ configuration and pricing rules.
- Data migration and integration dependencies.
- Features that have a direct supported migration path versus those requiring redesign.
- Performance and regression testing in a representative lower environment.
I'd also recommend doing an inventory of your current Vlocity metadata and integrations before starting the POC. That will give you a much better estimate of the migration effort and potential gaps.
If you can share which Vlocity clouds/modules you're currently using (for example, Communications, CPQ, Order Management, etc.), I can suggest a more targeted POC checklist.
