Separate history from active work
Select inactive records with archive policies and preserve them outside the operational workload. Source cleanup is a separate, gated lifecycle step.
Salesforce / Data Archiving
Salesforce Archive. Keep the history connected.
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.
Archive Manager
Your Salesforce archive, on your own SQL Server.
Storage
In Salesforce
62%
Data storage6.2 GB of 10 GB38%
File storage7.6 GB of 20 GBIn your archive
0
Archive dataStored in SQL Server0
Records archivedIncluding related recordsArchived by object
Nothing archived yet
Once a policy runs, each archived object appears here with its SQL table and record counts.
Start with your archiveProduct walkthrough · Sample data · Timing condensed
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.
- 01
Define the scope
Choose standard or custom objects. Use filters or SOQL to select records and preview the surrounding dependencies before the policy runs.
- 02
Capture and reconcile
Archive records and surrounding context. Track progress, review failures, and reconcile the source scope with the archived result.
- 03
Verify before any cleanup
Review captured records, relationships and files against the source scope. Source deletion is disabled by default and requires separate safety acceptance and operational controls.
- 04
Find and govern history
Browse archived records and related activity with the included viewer. Add licensed search or tabular reporting when your teams need it.
Inside Salesforce
History your team can use.
Keep archived records close to the people who need them. Choose the access and reporting modules for your deployment.
- Archive Viewer ? included
- Browse retained records, related activity and files from the Salesforce archive experience.
- Archive Search ? optional
- Find records by ID prefix and available typed name or subject fields. Search is separately licensed.
- Archive Reports ? optional
- Save personal tabular reports, apply AND filters, group by one field with record counts, and export CSV or formatted XLSX within configured limits.
On premises or in your cloud
Your database.
A defined deployment.
Choose where the data lives. Agree the engine, network access, permissions, storage capacity and recovery responsibilities before rollout.
Read the deployment guides| Database | What to plan for |
|---|---|
| SQL Server | Typed object tables, overflow fields and archive provenance in your database. Validate your intended on-premises or cloud-hosted installation. |
| PostgreSQL / MySQL | Deployment variants require separate review and acceptance. Confirm the supported host and archive features before selecting a destination. |
- Your infrastructure
- Place the archive service and database in your enterprise environment. Confirm the host, engine and installation acceptance for your selected deployment before rollout.
- Your database
- The reference archive implementation uses SQL Server. PostgreSQL and MySQL variants require a scoped deployment review and acceptance; engine support is not interchangeable across products.
- 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.
Before you begin
Know the scope.
Does archiving immediately delete records from Salesforce?
No. Capture does not remove source records. Destructive source cleanup is disabled by default pending safety acceptance. Any future reclamation requires separately validated controls, verification and approval.
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.
Start with your Salesforce data.
Bring the objects, files, destination and outcome you have in mind. We will define the scope and acceptance checks together.