Salesforce Data Archiving
Move the history. Keep the context.
Keep Salesforce focused on active work. Vivly Archive moves inactive records to your infrastructure while keeping the relationships, activity, and files that make that history useful.
Salesforce
Records, relationships, activity, files
Vivly Archive
Select → capture → verify
Your database
Historical context, ready to retrieve
Archive verification and production storage reclamation are separate decisions.
Make room for active work
Select inactive records with archive policies. Reclaim source storage after the archived result has been checked and removal approved.
Preserve the business story
Keep parent and child relationships, activities, conversations, and attachments connected to the record they describe.
Keep history accessible
Let teams search and review archived history inside Salesforce or through the Vivly Dashboard, under the archive’s access model.
The workflow
From archive policy to usable history.
Manage the complete lifecycle: define the record set, preserve its context, verify the result, and keep the history useful.
Define the scope
Choose standard or custom objects. Use filters or SOQL to select records and preview the surrounding dependencies before the policy runs.
Capture and reconcile
Archive records and surrounding context. Track progress, review failures, and reconcile the source scope with the archived result.
Approve reclamation
Decide when verified records may leave production storage. Apply the required write freeze and approvals before removal; archive without deletion when that control is unavailable.
Find and govern history
Search records, inspect related activity, and manage retention and holds. Review eligibility before using a recovery or rollback path.
Technical fit
Built around your operating environment.
Connect the product to your infrastructure, access requirements, and operational responsibilities.
- Your infrastructure
- Run the archive service and destination database in your enterprise environment. Plan the Windows, Linux, or Docker installation with your infrastructure team.
- Your database
- Use the database option that fits your deployment: SQL Server, PostgreSQL, or MySQL. Plan capacity, network access, and database backups together.
- Record integrity
- Preserve the business context required by your objects and relationships. Verification comes before reclamation; a successful copy alone does not authorise source deletion.
- Archive access
- Manage archive users and roles separately. The Salesforce archive viewer does not automatically replay live record sharing or field-level security.
Follow configuration, operation, and troubleshooting guides for your environment.
Explore the documentationQuestions worth asking.
Understand the scope before deciding how this fits your organisation.
Does archiving immediately delete records from Salesforce?
No. Capture, verification, and reclamation are separate stages. Source removal requires verification, approval, and the required operational controls, including a maintained write freeze. You can archive without deleting from Salesforce.
Where does archived data live?
The archive service, database, credentials, and operational backups live in customer-controlled infrastructure. Your team retains responsibility for the environment, its access controls, and its database recovery plan.
Can business users still see the history?
Yes. The Salesforce archive experience supports browsing objects, finding records, and viewing related activity and files. Archive access follows Vivly’s environment and role model rather than automatically inheriting live Salesforce sharing and field permissions.
Is archiving a replacement for backup?
No. Archiving manages inactive history and its accessibility. Backup protects recovery points against loss or unwanted changes. An archive can hold the latest captured record state without being an immutable series of historical snapshots.
See it with your workflow in mind.
Walk through your Salesforce environment, the records that matter, and the outcome you need. See how the product fits your team’s day-to-day work.