As of March 2026, we have started a process to migrate all customers from our legacy decision engine (OTS) to our new one (PAT).
Q: Is this necessary for everyone
A: Yes. We want all customers on the new engine. The old one will be retired as soon as it's no longer in use.
Q: What are the benefits?
A: Experience delivery is considerably faster - in many cases we've seen it run with half the response times of the current engine. We can also iterate faster on the new one, and so some features such as friendly names, multiple locations & segments per experience etc. become possible. UI response times are also considerably better, again over twice as fast for key actions.
Q: What if something goes wrong during migration?
A: Migration is isolated. We copy (not move/destroy) your data into a new database, and our team will then inspect all objects to see if they were copied over cleanly or not. You then have the ability to have a look around, and if we are all good we will then remove access to the legacy system.
Q: How long does migration take?
A: The script runs in seconds. Validation can take many hours as we want to be very sure things are fine/clean before progressing.
Q: Can we revert back if issues are found? Do we lose data if so?
A: Yes you can revert back. It will be a snapshot of the moment in time that we migrated, not including new things you've made since them. So reverting 1 day in won't be painful, but 1 month later would be.
Q: Where can I get support if I find issues?
A: Our normal support channels are the right way to reach out to us - JIRA tickets, emails, talking to your Consultant, etc.