Do we need both migration and archival?
No. Some projects need migration, some need an archive, and some need a selective combination. Start with what the replacement system must use and what staff only need for historical reference.
What can staff do with an archive?
Search for a record, open its report, follow related records and export a PDF. LiftShift Records also provides permissions, source context and controlled correction workflows. Your implementation defines the record types, search fields and report coverage.
Is LiftShift Records only for public safety?
Public safety is our primary focus. We also assess other legacy systems for archival and migration work. Tell us what is changing and how staff will need to use the retained information.
Where does it run?
In the customer’s environment or the hosting of an approved partner (software vendor). LiftShift does not host the records.
Do we need an existing software-vendor partner?
You can contact LiftShift directly about your records. If your software vendor is involved in the transition, we can include them in the discussion where appropriate.
How long does a project take?
The schedule depends on source access and clearances, report coverage, source complexity and customer review. An archival engagement moves through scoping, access, discovery, validation and production, with discovery and validation repeated for each report type.
Can records be changed?
Yes. Authorized users can correct a value and record the reason while keeping the source and correction history available. Changes to report layouts or mappings use the release review workflow. Record removal has separate permissions and requirements defined for the implementation.
What happens if the subscription ends?
The licensing approach provides continued read-only access to retained records, subject to the applicable license and continued hosting. Confirm which functions remain available and which support, update or integration services require an active subscription.