LiftShift Records

After implementation

Help with the records. A plan for later changes.

A question after launch may need an investigation, a corrected value or a new report. The support agreement defines how to raise it, who responds and what work is included.

Subscription and continued access.

LiftShift Records includes a 12-month active subscription. You can continue it after that for ongoing updates, support, integrations and corrections. If it ends, the archive stays available read-only. Staff keep access to your organization’s records and can still search them, open them and save them as PDFs.

Your data and continued access

How to raise a question about a report.

Identify the affected record or report type, what you expected and what you found. That gives the team a clear place to start. Your organization controls any access or data shared, and the support agreement sets how the issue is handled.

Changes are reviewed before they go live.

An investigation may lead to a record correction, a mapping fix or a revised report. Each follows the relevant permissions and review workflow. A correction to one record and a change affecting an entire report type need different checks.

New sources, reports and integrations get their own scope.

A new legacy source, report type or application connection can require new mappings, layouts and validation. We assess the request and define the work and responsibilities before implementation.

Who runs the archive is agreed at handover.

The customer or an approved partner (software vendor) owns the hosting responsibilities, including availability, backups and recovery. The license and support agreement define software assistance and updates. Keep those roles clear at handover so staff know where to take a problem.

Next step

Discuss support and terms.

Tell us whether you’re asking about an existing implementation, a new requirement or support and license terms.