Long-term customer projects

[gavin_rugg]

Hello there

We have situation where customer projects are required for a long-term period, typically indefinitely, but for example 10 years or more.

In this use case, customers are billed monthly on a T&E basis based on hours booked.

The system recommends projects/work packages to have a maximum of three years duration to avoid performance issues.

What is the advice on how to manage long-term engagements? Should they be setup for one year then extended continually (ie same project but eventually lasting for 10 or more years), or should a new customer project be setup each year for the client?

Anyone advice for long-term engagements like this would be appreciated.

Cheers
Gavin

[Feras_Al-Basha · Accepted solution]

Hi Gavin,

Thank you for sharing.

The recommendation to not have a project with many years of operation is not necessarily due to performance restrictions. The considerations to keep in mind is running revenue recognition jobs and handling foreign currency valuation over multiple years. Accordingly the suggestion is to typically break the long-term engagement into multiple engagements each ranging say 1-3 years. From a data migration perspective, historical data for projects is not recommended/supported to be migrated. The suggestion is to migrate the remaining open balance of a project to be billed.

Best regards,

Feras