Prod Migration FAQ

Between 8am and 10pm UTC on Saturday 13th April 2024, Kleene will conduct scheduled maintenance during which time the Kleene platform will be unavailable.

What are we doing?

Kleene is migrating our current production environment to a new network layout that is designed with security as the top priority. This migration is part of our ongoing commitment to providing you with the highest level of service and protection against potential threats.

During the migration process, it will be necessary for us to temporarily stop our current systems in order to take backups and transition them to the new environment. It's important to note that despite these necessary changes, our public IP address will remain unchanged. As a result, there will be no need for you to update the allowlist at your end.

While we anticipate that the migration process will be seamless and without disruption to our services after the maintenance window, unexpected issues may arise. In the event that things do not proceed as expected due to the migration, please rest assured that we will prioritise the resolution of any issues promptly and efficiently.

We understand the importance of maintaining the highest standards of security and reliability, and we appreciate your understanding and cooperation as we work to implement these enhancements.

When will this migration happen?

The date of the migration is 13th April. We will be in touch ahead of this date with reminders of the upcoming service disruption. Please stay tuned for updates.

What do I need to do?

There's no action required from Kleene customers at this moment. The public IP will not change for Kleene. However, if you have Kleene’s private IP added to the allowlist at your end, please reach out to CS representative for details.

Will there be any downtime?

The maintenance window is Saturday 13th April between 8AM and 10PM.
This means that Kleene will be inactive during this time. The reason for this is that the migration includes moving our underlying current cloud infrastructure to new AWS accounts with new network setup, improving scalability and reliability of the platform.

You will not be able to log into your Kleene account during the maintenance window.

What to expect during migration ?

Kleene services will be stopped completely during the maintenance window. It is expected during the downtime that any scheduled extracts and transforms will not execute. Any extracts or transform that are scheduled to start before 8am, but continue running into the maintenance window will be affected. However all extracts and transforms should run on their next existing schedule after the migration maintenance window finishes.

Note - If it can be avoided, please do not update your existing schedule so that your full pipeline runs before the maintenance window. Doing so may impact the performance of the system, therefore impacting already scheduled runs.

This migration does not include any changes to Kleene’s existing features or functionality.

What to expect after migration?

All functionality should work as expected. All scheduled extracts and transforms will run as per their schedule following this migration.

What will happen to extracts that bring in data for one day only?

(This advice is for extracts that load 1 day’s worth of data each day)
Please note that the below advice is based on standard configuration and the outcomes may vary depending on your extract configuration.

Append After missing 1 day of data - 2nd day will extract that day’s data and append to destination table

1 day will be missing

Append Incremental After missing 1 day of data - 2nd day will extract all data between the last date in destination table to that day’s data and append

0 days of data missing

Drop Create Load After missing 1 day of data - 2nd day will extract that day’s data and load to fresh destination table

1 days will be missing

Truncate Load After missing 1 day of data - 2nd day will extract that day’s data, clear the destination table and load into it

1 day will be missing

What can you do to backfill any missing data?

Backfill tasks will be needed for the missing days

  • Check the connector docs to see if backfill window is possible, this should give you specific details on each of your connectors.
  • Extract the missing days and insert into the destination table
  • Once data is restored, transform runs will generally pick up the missing data and update the pipelines

However there are some Connectors that do not facilitate backfill windows e.g. Google Ads , True-fit-360, Tik-Tok (display)

Transforms that are configured to work for the present day will be affected and might need to be run manually to cover the data from Saturday 13th April.

Will my data be safe during the migration?

Yes, data security is our utmost priority. The migration includes our compute services moving to new network layout within the same eu-west-1 region of AWS and there are no changes scheduled to data sources or warehouse.

Have you tested the migration steps?

Kleene completed a test-run of this process on 20th March 2024. The result of the test was successful. As part of our testing we ran an automated regression test that tests all functional features in the platform. We also manually ran tests on various parts of the system confirming the functionality works as expected.

As part of our testing we also tested a wide range of connectors and their functionality.

What happens in case something doesn’t work?

In case of any unforeseen issues during the migration, a roll back plan is in place.

Roll Back plan for migration:
If there are problems up to 10 hours into the migration, we will execute a roll back to the previous state.

Roll Back plan on the day of migration:
As a high level plan we will repoint the DNS to current production. However any scheduled run missed during the migration will still be affected. In the event of roll back , we will capture the results for analysis and work towards a maintenance date in the future.

Kleene has a rigorous testing process already in place, this means that we are well placed to run tests to validate the migration.

It should be noted that once we have completed the migration successfully, a full roll-back will not be possible. Any issues that are found as a result of the migration will be resolved on a case-by-case basis. There is a chance that customers may experience data loss as part of missed schedule runs (where backfill is not supported) or system failure that occurs after the migration. The best course of action in this scenario would be to identify the issue and report it to the Kleene support team for resolution.

Who can I contact if I have questions?

Please contact our support team at or CS member if you have any questions or concerns about the migration.