Data archival services
Retire the old system
and keep its data.
We move the old system’s data into LiftShift Records, either on its own or alongside a migration. Our team extracts the data, sets up the searches and reports your staff need, and checks them with you so the old system can be retired.
What we do
From the old system
to reports your staff can use.
We scope each archive around the system and the people who still use its data. The work usually covers these four parts.
Data extraction
We get the data out of the old system, along with the files that belong to it.
Archive design
We work out with you how far back the archive goes, which report types it needs and who should see what.
Searches and reports
We set up the searches, report layouts and links between records in LiftShift Records.
Review and handover
Your reviewers check each report type with us, and then we hand over an archive your team can run.
How an archive is built
Five stages, from scoping to production.
Discovery and validation repeat for each report type in scope.
Scoping
Agree on the scope, responsibilities and terms.
Access
Arrange data access, files and required clearances.
Discovery
Understand the source and configure each report type.
Validation
Review the records, resolve findings and recheck changes.
Production
Make the approved reports available to the intended users.
What stays available
Fields your new system can’t hold
stay in LiftShift Records.
LiftShift Records keeps all the columns from the exported legacy data, even the ones your new system has no place for. Staff find records with the searches we set up, read each one in the report layout they already know and can save it as a PDF.
Before you start
Common questions
Do we need a migration too?
Not always. Archival can stand on its own, with the new system starting clean and the legacy data going to LiftShift Records. It can also run alongside a migration.
Who hosts the archive?
The customer or an approved partner (software vendor). The project names who runs access, backups, updates and support.
When can the old system be retired?
When the customer has accepted the archive and nothing else still depends on the old system. That decision is the customer’s to make.
Start with one system
What does the old system still hold?
Tell us about the system being retired and what people still need from it. You don’t need a source inventory to begin.