> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/technical/guides/installation/opencrvs-maintenance-tasks/off-boarding-from-opencrvs.md). # Off-boarding from OpenCRVS Perhaps you may wish to manually decrypt and extract the raw data from an encrypted OpenCRVS backup file if migrating the data to another vendor's civil registration system. Each daily backup directory on the backup server (`/home/backup//`) contains one encrypted archive per datastore: * `postgres_backup_.tar.gz.enc` * `minio_backup_.tar.gz.enc` Using the BACKUP\_ENCRYPTION\_PASSPHRASE the backup archives downloaded in the **Disaster Recovery Procedure** can be decrypted and unzipped (extracted) like this: **Decrypt:** ``` openssl enc -d -aes-256-cbc -salt -pbkdf2 -in postgres_backup_${DATE_OF_REQUIRED_BACKUP}.tar.gz.enc --out postgres_backup_${DATE_OF_REQUIRED_BACKUP}.tar.gz -pass pass:$BACKUP_ENCRYPTION_PASSPHRASE ``` Repeat the same command for the `minio_backup_${DATE_OF_REQUIRED_BACKUP}.tar.gz.enc` archive. **Extract the raw data into a directory named "extracted\_data":** ``` mkdir extracted_data tar -xvf postgres_backup_${DATE_OF_REQUIRED_BACKUP}.tar.gz -C extracted_data ``` The PostgreSQL archive contains one `.dump` file per database, created with `pg_dump` in custom format (restore it with `pg_restore`), and a `roles.sql` file with the database roles (without passwords). The MinIO archive contains the supporting document attachments as plain files. You can now write whatever custom migration script you wish using the raw PostgreSQL and MinIO files. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.opencrvs.org/technical/guides/installation/opencrvs-maintenance-tasks/off-boarding-from-opencrvs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.