Exit options & handover

You choose the commitment: cooperation can be ongoing with a notice period, or a fixed term, such as a three-year term with fixed prices.

Individual phases and work packages are agreed as Work Orders, and ending one work package does not end the wider cooperation.

During a fixed term, the agreed recurring fees and unit prices stay fixed.

What happens when the term ends — renewal, notice and any price adjustment — is agreed in advance. An adjustment at renewal is limited to inflation and announced in advance.

New modules agreed during the term have their own scope and commercial terms.

Notice is given in writing. The notice period and the final date are agreed in advance, so you know exactly when the cooperation and the regular payments end.

You can leave early. If the price or delivery arrangement was based on a multi-year commitment, the financial consequence of an early exit is agreed before signing, so there are no surprises.

It does not apply if ReApptor materially fails to meet its obligations.

Technical handover and optional transition support are explained separately, so you can evaluate the full cost of changing provider in advance.

An implementation exit right can be included: if the agreed core scope is not delivered as specified, you can exit without licence fees for the rest of the term.

The parties can also jointly agree that the solution or cooperation is not the right long-term fit. In both cases, all IPR and handover protections continue to apply.

The exit package covers the customer-specific assets needed to continue the solution: source code, configuration, data structures, deployment and automation scripts, and documentation.

It also includes the project deliverables and the backlog or requirements material the incoming team needs. You receive owner-level access to the transferred customer-specific repositories.

Reusable components published under open-source licences remain usable after exit; ReApptor's other reusable platform components keep their own licence terms.

Yes. The existing production environment and the relevant operational accounts can be transferred to you, without rebuilding the environment.

Access and account reassignment is completed within two weeks after you are ready to receive the environment.

Moving to another cloud or replacing services is a separate migration with its own planning and validation.

No. Access and asset handover, knowledge transfer and migration to a different environment are distinct activities.

Access and asset handover are free of charge. Optional paid support is separate: guidance for the incoming team (20–40 hours) or a fixed 60-hour full-support migration package, charged at the hourly rates of our price list. You can choose either option or neither.

Termination assistance is provided at your request, to you or to the new supplier you appoint. It can begin before the final service date and continue for up to three months afterwards.

Yes. Ending one Work Order is not the same as ending the whole cooperation: handover and assistance then relate to that work package and its deliverables, while other work and services continue.

This allows a change to be planned around the part of the solution that is actually changing.

Each party's responsibilities, the agreed quality criteria and liability are defined in advance, so both sides know what to expect.

If a disagreement arises, the parties first seek to resolve it through negotiation.