Use this checklist to identify the business, data, integration, compliance and cutover work that should be understood before a Veeva CRM to Salesforce Life Sciences Cloud migration.
Current environment
- Number of orgs and countries
- Users, profiles and permission sets
- Territory structures and alignment
- Mobile usage and offline requirements
Data
- HCP/HCO accounts and affiliations
- Calls, events and samples
- Consent and preferences
- Historical activity and custom objects
Metadata
- Custom objects and fields
- Layouts, validation rules and flows
- Apex and Lightning components
- Reports and dashboards
Integrations
- MDM, ERP and data providers
- Marketing, content and sample systems
- Consent and medical information
- Identity and analytics
Integrations are usually where hidden complexity lives.
Business processes
- Call planning and reporting
- Account planning
- Medical engagement and events
- Sampling, consent and service
Compliance
- Retention and auditability
- Security and privacy
- Traceability and change control
- Reconciliation evidence
Testing
- Unit, system and integration
- Regression and migration testing
- Security testing and UAT
- Applicable validation activities
Cutover
- Freeze and final extract
- Delta migration and reconciliation
- Integration activation and go/no-go
- Rollback plan and hypercare
Go deeper on the two biggest workstreams: Veeva CRM data migration and integration migration. For the full delivery approach, see our Veeva to Salesforce migration services.
Turn this checklist into a migration roadmap
Our readiness assessment works through each item against your actual environment and produces a sequenced, risk-ranked plan.