# Error migrating from version 3x to 4x

**URL:** <https://discuss.zetetic.net/t/error-migrating-from-version-3x-to-4x/6360>\
**Category:** Issues\
**Created:** [April 1, 2024, 8:40am UTC](https://discuss.zetetic.net/t/error-migrating-from-version-3x-to-4x/6360 "2024-04-01T08:40:40Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![developernotes](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/developernotes/32/1309_2.png) [@developernotes](https://discuss.zetetic.net/u/developernotes)\
**Post date:** [April 1, 2024, 1:02pm UTC](https://discuss.zetetic.net/t/error-migrating-from-version-3x-to-4x/6360/3 "2024-04-01T13:02:20Z")

</div>

Hello @ITService_Developer, @Venkat,

When upgrading from SQLCipher version 3.x to 4.x, the 4.x library will not open a 3.x database file by default. There are a few options available to address this, please review the upgrade notes here to determine how you would prefer to proceed:

> [@Upgrading to SQLCipher 4](https://discuss.zetetic.net/t/upgrading-to-sqlcipher-4/3283):
>
> The recent release of [SQLCipher 4](https://www.zetetic.net/blog/2018/11/30/sqlcipher-400-release/) introduces many new performance and security enhancements for applications that use SQLCipher for secure local data storage. However, the introduction of new default algorithms, increased KDF iterations and a larger page size means that SQLCipher 4 will not open older databases by default. This document provides guidance on the upgrade options available to applications that have previously integrated SQLCipher versions 1 through 3. Option 1: Database File Migr…

---

_[View the full topic](https://discuss.zetetic.net/t/error-migrating-from-version-3x-to-4x/6360)._
