Overdue software updates
Check which components need updating and test the changes before publication.
Modernization and maintenance
We fix errors, add features or replace components that are no longer maintained. Before making changes, we identify the data to preserve and the services that must stay available.
Tell us what is not working
Check which components need updating and test the changes before publication.
Review the available code and documentation to establish what it would take to continue the project.
Plan the transfer, data checks and any downtime. Establish how to restore the previous version.
The choice depends on the findings, cost and acceptable downtime. A change does not always require a complete rebuild.
Review the code, data, update process and connected systems within the approved access.
Address problems that prevent people from using the application. Schedule other changes separately.
Migrate or rebuild one component at a time, with a way to restore the previous version where practical.
Document updates, backups and checks after each change. Agree separately on the maintenance and support included in the project.
Tell us what is not working and what you have tried. Mention missing source code or documentation. Do not send passwords.
After the assessment, we agree what needs attention now, what can wait and what can be changed in stages.
Describe the problem and what you have already tried. We can start with a technical assessment.