rtogtor
Migrate data between PostgreSQL and Neo4j, in either direction, with explicit mappings, plans you can inspect before writing, resumable runs and value-level verification.
Version 1.0. The mapping's direction decides the way:
relational-to-graph reads PostgreSQL and writes Neo4j, graph-to-relational
reads Neo4j and writes PostgreSQL. See the
compatibility matrix.
Each wheel bundles the RtoGtoR engine for its platform (Linux x86_64/aarch64, macOS 12+ x86_64/arm64, Windows x64). The SDK runs the engine as a child process. All migration logic runs in the engine, which behaves identically for every RtoGtoR SDK.
Install
pip install rtogtor
Use
from rtogtor import Connection, Mapping, Migration
source = Connection.postgresql(url_env="SOURCE_URL")
destination = Connection.neo4j(uri="bolt://localhost:7687", auth_env="NEO4J")
mapping = Mapping.from_file("mapping.yaml")
with Migration(source=source, destination=destination, mapping=mapping) as m:
plan = m.plan() # nothing is written
report = m.run(dry_run=False)
verification = m.verify(report.run_id, values=True) # every value, both sides
A complete program, migrating the example both ways: examples/ecommerce/python.
- Credentials come from environment variables:
SOURCE_URL, plusNEO4J_USERandNEO4J_PASSWORDforauth_env="NEO4J". They are never sent in protocol messages or printed. - Errors are
RtoGtoRErrorwith a stablecode(ErrorCode.MAP_005, …),severityandretryable. Invalid mappings list every problem indiagnostics. - Resuming: if a run fails, is interrupted or you press Ctrl-C, the error
carries the
report. Passreport.run_idasresume_run_id. Committed batches are not repeated, and nothing is duplicated. - Retries: transient errors are retried per
retry=RetryPolicy(...)(default 3 attempts, 200 ms to 5 s backoff). - asyncio:
AsyncMigrationoffers the same methods as coroutines. - Typed model:
rtogtor.modelsholds Pydantic models generated from the specification's JSON Schemas. - CLI:
python -m rtogtor plan --mapping mapping.yaml --source-env SOURCE_URL.
Learn more
License: Apache-2.0.
Metadata
Release files for rtogtor 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| rtogtor-1.0.0-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for rtogtor-1.0.0-py3-none-win_amd64.whl |
| rtogtor-1.0.0-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.musllinux_1_1_x86_64.whl | Python 3 | none | Linux musl 1.1+ x86-64, Linux glibc 2.17+ x86-64 | Details for rtogtor-1.0.0-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.musllinux_1_1_x86_64.whl |
| rtogtor-1.0.0-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.musllinux_1_1_aarch64.whl | Python 3 | none | Linux musl 1.1+ ARM64, Linux glibc 2.17+ ARM64 | Details for rtogtor-1.0.0-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.musllinux_1_1_aarch64.whl |
| rtogtor-1.0.0-py3-none-macosx_12_0_x86_64.whl | Python 3 | none | macOS 12.0+ x86-64 | Details for rtogtor-1.0.0-py3-none-macosx_12_0_x86_64.whl |
| rtogtor-1.0.0-py3-none-macosx_12_0_arm64.whl | Python 3 | none | macOS 12.0+ ARM64 | Details for rtogtor-1.0.0-py3-none-macosx_12_0_arm64.whl |
Total release size: 21.5 MB
Release files / rtogtor-1.0.0-py3-none-win_amd64.whl
| Download URL | rtogtor-1.0.0-py3-none-win_amd64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
59e84d2c08896130d4d5b779337f705d0bf53f19d47cea64f7956c75cadb3389
|
|
BLAKE2b-256 checksum How to use checksums |
ed28a855a46e46ccd1e57b16bbde290eae87a993960dac7cb817f7e89e395c36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 30, 2026.
Transparency logRelease files / rtogtor-1.0.0-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.musllinux_1_1_x86_64.whl
| Download URL | rtogtor-1.0.0-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.musllinux_1_1_x86_64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | Linux glibc 2.17+ x86-64 Linux musl 1.1+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
56c0bfadcbb93b0a4f9d2681b78d9faaafd9115a1ee1af710b2404119ddcf32e
|
|
BLAKE2b-256 checksum How to use checksums |
8117b6bb46e521cd4950659bd25beaf4f4886e9b425bf85c0941cb42737906fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 30, 2026.
Transparency logRelease files / rtogtor-1.0.0-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.musllinux_1_1_aarch64.whl
| Download URL | rtogtor-1.0.0-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.musllinux_1_1_aarch64.whl |
|---|---|
| Size | 4.0 MB |
| Tags | Linux glibc 2.17+ ARM64 Linux musl 1.1+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
46c0f45ae4fd8530f81523495c265690ceb94f60857af13a06134dd28298e824
|
|
BLAKE2b-256 checksum How to use checksums |
546e43ca2c7553405b5dfae7a6809978de6826f8c36cb7af8dc5bf3de4f13334
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 30, 2026.
Transparency logRelease files / rtogtor-1.0.0-py3-none-macosx_12_0_x86_64.whl
| Download URL | rtogtor-1.0.0-py3-none-macosx_12_0_x86_64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | Python 3 macOS 12.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
286f6541129f6e71e8bfeb66347fbaa950663616a0a45980f16d7165781ea309
|
|
BLAKE2b-256 checksum How to use checksums |
edeea6e2b4fc5c339e36795f82b4c09a67f234b11f34e98f9a1bca93a8c9e39c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 30, 2026.
Transparency logRelease files / rtogtor-1.0.0-py3-none-macosx_12_0_arm64.whl
| Download URL | rtogtor-1.0.0-py3-none-macosx_12_0_arm64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | Python 3 macOS 12.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
17b8a0386bc523fcd00194dea471a0c67f9bff318fd3439e2c48986968d42d95
|
|
BLAKE2b-256 checksum How to use checksums |
ee1634ef666bbeb287ce8a717e1f4b0b621f0dac193d5ee7b9214182abf4c27f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 30, 2026.
Transparency logSecurity for rtogtor 1.0.0
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 5 files in this release have been uploaded with provenance metadata.
Attestation for rtogtor-1.0.0-py3-none-win_amd64.whl
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 Oct 30, 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.