What runs alongside the standard system?
Custom developments matter as much as the product and version. List reports, transfers, scheduled tasks and additional tools used in daily work. Record what each does and who uses it.
Access and ownership are different
Being able to sign in does not mean you own the source code or have the right to modify it. Review licences, source access, maintenance responsibilities and documentation separately. Agreements with the previous supplier may affect these boundaries.
A backup must also be restorable
Know the backup schedule, storage location and responsible person. “We have a backup” is not enough without a planned restore test in a controlled environment. Production-data access and work scope require separate agreement.
Hand over open tasks and recurring issues
Pending requests, temporary fixes and period-specific errors should be explained to the new team. Prepare sanitised error examples and reproduction steps where possible. Knowing a problem’s cause is different from knowing a workaround.
Do not fix the support scope before reviewing it
Monthly support needs depend on users, process complexity, custom developments and on-site work. At ER-TE, we prefer to define the initial review and then document support boundaries so that inclusions are clear from the outset.
Integration & custom software
A solution shaped around the way your business works.
Explore solutionGeneral project preparation guidance. Product features and migration terms depend on the version and licence and require separate assessment. Product reference: Logo Yazılım.