ServiceNow Data Archiving
Keep service history useful.
Closed work still matters to your customers and operations teams. Preserve ServiceNow records, reference relationships, and attachments in your own database, with history you can retrieve beyond the original workflow.
ServiceNow
Selected tables, fields, and related records
Archive copy
Resumable capture and attachment preservation
Your database
Stored context and independent retrieval
Copying preserves history. Source deletion and production storage reclamation are separate lifecycle decisions.
Own your service history
Keep historical data in a database you control. Build a retrieval path for instance retirement, consolidation, or long-lived operational records.
Keep the surrounding context
Preserve explicitly selected reference relationships and attachments alongside the primary records. Include the journal and audit tables your history requires.
Make history readable
Inspect preserved records and context through the archive viewer. Verify that the information your teams need remains useful beyond the source workflow.
The workflow
A clear path to independent history.
Start with a defined record family. Keep selection, copying, and retrieval visible so service owners can verify the archive.
Select the record family
Choose closed incidents, completed requests, or another table set. Explicitly include the reference records, journal history, and attachments required to explain it.
Define the archive plan
Set table and field scope, record filters, and an age cutoff. Review the destination and the source identity before starting the copy.
Copy with visible progress
Capture records and attachment bytes in the destination database. Track archive runs and use resumable checkpoints to continue interrupted work.
Verify independent retrieval
Inspect fields, reference links, and verified attachments. Confirm the required history is readable with source access disconnected before retiring an environment.
Technical fit
Built around your operating environment.
Connect the product to your infrastructure, access requirements, and operational responsibilities.
- Explicit scope
- Standard and custom tables are selected deliberately. Source permissions govern capture, and related records must be included in the archive plan.
- Customer-owned storage
- Store archive data in SQL Server, PostgreSQL, or MySQL. Define capacity, database backup, network access, and operational ownership.
- Access after capture
- Archive retrieval needs its own access model. Stored history does not automatically replay the current source ACLs or changes made after capture.
- Lifecycle decisions
- Copying is separate from deletion. Keep retention, source retirement, and any removal approvals explicit; copying alone does not reclaim instance storage.
Follow configuration, operation, and troubleshooting guides for your environment.
Explore the documentationQuestions worth asking.
Understand the scope before deciding how this fits your organisation.
How do we choose what to archive?
Use an explicit table and field scope with record filters and an age cutoff. Include the reference records, journal history, audit data, and attachments needed to make the result useful. Related records are not collected indiscriminately.
Does an archive copy remove source records?
No. The archive copy preserves records in your destination database. It does not delete source records, reclaim instance storage, or replace the approvals needed for source retirement.
Can we keep history after retiring an instance?
Independent retrieval is the goal: preserve the required data, then verify archive reads with the source disconnected. Confirm your export rights, completeness, retrieval needs, and access controls before ending source access.
How are files and references handled?
The archive preserves selected references and downloads explicitly scoped attachment bytes. Include the related table and attachment scope in the plan, then verify file integrity and the links to their parent records.
See it with your workflow in mind.
Walk through your ServiceNow environment, the records that matter, and the outcome you need. See how the product fits your team’s day-to-day work.