Jitsu Classic

In August 2024, we introduced Jitsu 2.0, the successor to the original version of Jitsu (now referred to as Jitsu Classic). Since then, we have been supporting both versions concurrently to ensure a smooth transition for our customers.

However, maintaining two versions limits our ability to focus on innovation and delivering the best possible experience. To prioritize Jitsu 2.0’s continued growth and improvements, we’ve made the decision to sunset Jitsu Classic. We’re here to support you with detailed migration guides and assistance to make this transition as seamless as possible.

To streamline the transition, Jitsu 2.0 introduces backward compatibility with Jitsu Classic at the events endpoint level. The effort required to migrate to Jitsu 2.0 requires minimal changes on the client side — specifically, updating the Jitsu host and write key.

That being said, if you have more resources, you can switch to a native Jitsu 2.0 client and protocol.

To start with migration, please see:

• What Changed — summary of differences between Jitsu Classic and Jitsu 2.0
• Step by Step Guide using Compatibility Endpoints - detailed step by step guide on how to migrate from Jitsu Classic to Jitsu 2.0 using compatibility endpoints
• Sending Data - detailed guide on how to send data to Jitsu 2.0, if you're willing to switch to native Jitsu 2.0 client and protocol