You are here:
Migrate Privacy Center from Heroku to Hyperforce
To prepare for the retirement of the legacy Heroku-based store, transition your data governance to the secure Hyperforce architecture. Recreate your policies and migrate your records to Privacy Center 2.0 or Archive to take advantage of faster performance, advanced filtering, and seamless sandbox testing.
Required Editions
| Available in: Developer, Enterprise, Performance, and Unlimited Editions with the Privacy Center license. |
| User Permissions Needed | |
|---|---|
| To create and manage Privacy Center policies: | Modify All Data AND Manage Privacy Policies |
Why Migrate?
Salesforce is retiring the legacy version of Privacy Center that uses Heroku for the backend retention store. This initiative modernizes your data governance architecture with a platform that offers instant provisioning, advanced policy logic, and seamless sandbox testing.
Choose Your Migration Path
Your migration path depends on your primary business use case.
- Privacy Center 2.0: Choose this path if your needs are compliance-driven, such as Consent Management, Right to Be Forgotten (RTBF), and Data Subject Access Requests (DSARs).
- Archive: Choose this path if your needs are primarily data retention-driven to manage storage and prevent overages.
Review the Privacy Center Migration Planning slides for strategic decision support.
Migration Checklist
Complete these phases in order to ensure data integrity and maintain proper versioning.
Phase 1: Preparation and Environment
- Request Org Permissions: Contact your Account Team to have the Privacy Center Migration or Archive Migration org permission enabled.
- Environment Note: You must perform data export and movement in a production environment because the Heroku Connect interface and Hyperforce retention store are tied to your production org.
Phase 2: Recreate and Assess
- Recreate Policies: Manually recreate your legacy Heroku policies as Data Management or RTBF policies on the new architecture. Testing in a sandbox before moving to production is recommended.
- Assess Legacy Data: Use Heroku Dataclips or the Heroku CLI to review records currently stored in the cache schema to determine what must be moved.
Phase 3: Data Migration
- Privacy Center 2.0: Use the Cervello migration app to move data from Heroku into temporary Salesforce custom objects, then run your recreated policy to move that data into the Hyperforce retention store. See the Privacy Center Migration Planner for app setup and steps.
- Archive: Export retained data from the legacy Heroku store (for example, by using CSV export as described in the Privacy Center Migration Planner), then import it into Archive using your own S3 bucket or by uploading CSV files from your local machine.
- Assistance: For complex implementations, you can engage Salesforce Services or our premier Privacy Center partner, Cervello.
Phase 4: Cleanup and Finalization
- Remove Heroku Components: Delete your Heroku Private Space and Privacy Center app.
- Uninstall Managed Package: After migration is verified, uninstall the legacy Salesforce Privacy Center managed package to remove old configuration settings.
Constraints and Considerations
- Avoid Mixed Data: Migrate all legacy data before retaining new data to avoid overwriting records; our versioning logic prioritizes the most recent record.
- Regional Support: Certain regions, such as Brazil, Indonesia, Middle East, and South Korea, are currently unsupported for Hyperforce data retention.
- Government Cloud: Data retention isn’t currently available in Government Cloud for either Heroku or Hyperforce.
