Migrating from v1

August 16, 2025

There has been several major changes to the c15t backend since v1. For the most part, the migration should be straightforward.

Notable Changes

  • @c15t/backend/v2 now uses FumaDB to integrate with a variety of databases.
  • @c15t/backend/v2 stores date & time as EPOCH milliseconds instead of ISO strings.
  • @c15t/backend/v2 has a slightly different instance interface.
  • @c15t/backend/v2 does not support custom prefixes or table names.

Info

As your consent backend is less production-critical, it could be worth statrting with a new database and doing a data migration. This ensures your databases schema 100% matches the new FumaDB schema.

Migratiing your database

If you encounter any issues, and your schema has not been altered e.g. custom prefixes or table names. You can run the following SQL add the table FumaDB expects.