Archiving Salesforce data while keeping history accessible
Move historical records into your own database and keep them accessible inside Salesforce. This demo follows a policy from selecting records to opening the archived history.
About the archive
The demo uses Salesforce as the source and SQL Server as the archive database. A policy selects Cases and captures supported related records so the history stays useful beyond the original record.
Cases, account references and the information that explains the relationship.
Emails, comments and supported activity connected to those records.
Supporting documents, with file content captured when download mode is enabled.
Choosing what to archive
Create a policy, choose the object and set its criteria. The dashboard lets you preview matching records before running and choose a schedule for recurring work.
Following the archive job
Follow the work as Vivly collects record IDs, archives the parent records, then captures related records and files. The job keeps its progress and results available for review.
Find records matching the policy.
Capture the selected Cases.
Keep supported related history.
Capture supported content in the configured mode.
Check completeness and any gaps.
Keeping the archive in your database
Vivly writes the selected history into customer-controlled storage. For the SQL Archive deployment, that means your SQL Server, hosted on premises or in your cloud environment.
Vivly ArchiveCapture and reconcile
Your SQL ServerRetained records and structureReviewing the copy before freeing storage
Check the archive before approving source removal. Copying records and deleting them from Salesforce are separate decisions. Review record completeness and captured file bytes so the history you need is preserved.
Accessing history inside Salesforce
Vivly’s Lightning Web Components (LWCs) bring archived history into Salesforce. Add the Viewer to record pages or open a standalone archive tab, so your team can read historical information where they already work.
Read record details, related cases, emails and timelines. Open the archived files you are authorised to access.
Find archived records by supported readable fields and record IDs, then open them in the Viewer.
Choose columns, filter and group records, save personal reports and export authorised results to CSV or Excel.
Viewer is included in the base experience. Search and Reports are optional modules, enabled for approved users through the matching licence and Salesforce permission sets.
Explore Viewer, Search & ReportsControl who can see and manage the archive
Moving history out of Salesforce should not make it open to everyone. Vivly combines approved users, Salesforce object and field permissions, and record-level access to govern the archive.
A Salesforce sign-in starts an access request. The owner approves membership for the right environment and assigns a named seat.
Object and field permissions restrict what readers can see. Record access also needs a verified Salesforce access check or an explicit archive grant.
Owners grant or revoke access to selected archived records. These boundaries apply to browsing, Search, Reports, exports and authorised files.
Use access history and the operational audit trail to review user activity and archive jobs. Administrative operations stay separate from ordinary reading.
Archive access is managed explicitly. Salesforce sharing rules are not automatically copied in full; browsing, Search and Reports rely on archive grants. The matching Salesforce components and Archive runtime must be deployed together for these controls.
Explore security & accessPlanning your deployment
Start with the records you need to retain, the database your team manages and the people who need access. Agree the archive policy, file capture, user permissions and recovery responsibilities with your application owner and DBA.
Your environment
Run on your infrastructure, on premises or in your cloud environment.
Archive databases
SQL ServerMain Windows Archive packageOperating systems & packaging
We confirm the host, database and package together for your deployment. Database options are product-specific; they are not interchangeable settings in the Windows installer.
Common questions
Where is the archive stored?
The main Windows Archive distribution uses your SQL Server. Snowflake has a separate distribution and acceptance process. The deployment page explains the product-specific options.
Does archiving automatically delete Salesforce records?
No. Copy, reconciliation and source removal are separate operations. Reclaiming storage requires an approved removal workflow after verifying the archive.
Are Search and Reports included?
Viewer is the base experience. Search, Reports and file storage have separate entitlements; the proposal identifies your modules, users and orgs.