This release is a pre-release and may not be stable for production use.
zodb-convert
Generic ZODB storage conversion tool. Copies data between any two ZODB-compatible storages.
Derived from RelStorage's zodbconvert by the Zope Foundation and Contributors, extracted as a standalone generic tool.
Installation
pip install zodb-convert
To convert between specific storage types, install their packages too:
pip install zodb-convert ZODB RelStorage # FileStorage ↔ RelStorage
pip install zodb-convert ZODB zodb-pgjsonb # FileStorage ↔ PGJsonb
Usage
Traditional config file
Create a config file (convert.conf):
<filestorage source>
path /data/Data.fs
blob-dir /data/blobs
</filestorage>
<filestorage destination>
path /backup/Data.fs
blob-dir /backup/blobs
</filestorage>
For storages that need blob wrapping:
<blobstorage source>
blob-dir /data/blobs
<filestorage>
path /data/Data.fs
</filestorage>
</blobstorage>
<filestorage destination>
path /backup/Data.fs
blob-dir /backup/blobs
</filestorage>
For third-party storages, use %import:
%import relstorage
<relstorage source>
<postgresql>
dsn dbname=zodb user=zodb
</postgresql>
</relstorage>
<filestorage destination>
path /backup/Data.fs
</filestorage>
Run:
zodb-convert convert.conf
Using existing zope.conf files
Extract storage configuration directly from Zope config files:
zodb-convert --source-zope-conf /old/etc/zope.conf --dest-zope-conf /new/etc/zope.conf
Specify which database to use (defaults to "main"):
zodb-convert --source-zope-conf zope.conf --source-db main \
--dest-zope-conf other.conf --dest-db catalog
Mixed mode
Combine traditional config with zope.conf extraction:
zodb-convert convert.conf --source-zope-conf /old/etc/zope.conf
Where convert.conf contains only the destination storage section.
Options
--dry-run— show what would be copied without making changes--incremental— resume from the last transaction in the destination-w N/--workers N— number of parallel writer threads (default: 1)--background-blobs— upload blobs to S3 in a background thread pool, decoupled from PG writes (faster for large migrations)--deferred-blobs PATH— write blob upload tasks to a manifest file instead of uploading during migration--upload-blobs MANIFEST— upload deferred blobs from a manifest file (created by--deferred-blobs)-v/--verbose— increase verbosity (-vfor INFO,-vvfor DEBUG)
Source Code and Contributions
The source code is managed in a Git repository, with its main branches hosted on GitHub. Issues can be reported there too.
We'd be happy to see many forks and pull requests to make this package even better. We welcome AI-assisted contributions, but expect every contributor to fully understand and be able to explain the code they submit. Please don't send bulk auto-generated pull requests.
Maintainers are Jens Klein and the BlueDynamics Alliance developer team. We appreciate any contribution and if a release on PyPI is needed, please just contact one of us. We also offer commercial support if any training, coaching, integration or adaptations are needed.
License
ZPL-2.1 — see LICENSE.txt
Metadata
Release files for zodb-convert 1.0.0b12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zodb_convert-1.0.0b12.tar.gz | 52.8 kB | With provenance | Details for zodb_convert-1.0.0b12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zodb_convert-1.0.0b12-py3-none-any.whl | Python 3 | none | any | Details for zodb_convert-1.0.0b12-py3-none-any.whl |
Total release size: 68.7 kB
Release files / zodb_convert-1.0.0b12.tar.gz
| Download URL | zodb_convert-1.0.0b12.tar.gz |
|---|---|
| Size | 52.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
211f8ba473e51574c06ed40e3edc3b9c0030bf68c832560d9a86396f48403026
|
|
BLAKE2b-256 checksum How to use checksums |
e1f3b69e9b69a3fedf32869ed9e714835a7836b30da14877326d6ed911115cd5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 31, 2026.
Transparency logRelease files / zodb_convert-1.0.0b12-py3-none-any.whl
| Download URL | zodb_convert-1.0.0b12-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cee8a8aa099c695a2e1087877370ef6defecdf4682d3b97cb1888b3062d9c873
|
|
BLAKE2b-256 checksum How to use checksums |
04b3028167a1de8e719c63c2ed308984b48e55365272afc0ae8e3e9e282e44f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 31, 2026.
Transparency logSecurity for zodb-convert 1.0.0b12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for zodb_convert-1.0.0b12.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 31, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.