Five questions to frame the next step
Start with what people need to do after the system changes. This quick check helps separate the work the new application needs from the history people still need to use.
Take the five-question checkThe right approach can include both.
Your situation
The first three answers guide the suggested approach. Data quality and timing add questions to plan around.
Use “Not sure” wherever you need to confirm a dependency.
Use “Not sure” wherever you need to confirm a dependency.
The options, together
Migration and archival address different uses of historical information. A selective combination can serve the same transition.
Move the information the replacement system needs for ongoing work and its own workflows.
Define the records to move, destination requirements, mappings and review.
Move a defined set into the replacement system and keep the remaining data available in LiftShift Records.
Agree on the split, the reports people need and any optional integration.
Keep historical records available for search, reference and export alongside the replacement system.
Confirm the required reports, relationships and files, plus any remaining dependencies.
An integration is optional work within the agreed scope. It is not assumed by the results of this check.
From a question to a plan
A customer transition, a replacement project or an old system kept running for lookups is enough to start.
