Mode Migration
Organization administrators can copy selected library data between a Cloud setup and a Local setup. Migration preserves the source and merges into the destination without silently overwriting existing records.
Before you begin
- Update both setups to compatible Libcodesk versions.
- Create and configure the destination organization and its libraries first.
- Confirm that you can sign in as the organization administrator.
- Keep the Standalone app open and connected during a Cloud transfer.
- For Cloud-to-Standalone migration, allow the app to create and verify its safety backup before continuing.
Start from the Standalone app
- Open Settings > Mode Migration.
- Choose Standalone to Cloud or Cloud to Standalone.
- Check the Cloud connection URL. You may keep the configured Libcodesk Cloud address or enter another compatible HTTPS Cloud endpoint, just as in the setup wizard. Select Test Connection after every URL change; sign-in remains unavailable until that connection succeeds.
- Sign in with the Cloud organization administrator account. The password is used only for authentication and is not saved in migration history.
- Select the destination organization and map each source library to the correct destination library.
- Select the data categories. Required dependencies are selected automatically; for example, circulation also requires members and collection data.
- Review record counts, file size, warnings, source, destination, and the conflict policy.
- Confirm that you understand the settings, then start the migration.
The page shows the active stage, records processed, measured speed, changing estimated time, conflicts, and failures. You may pause a running job and resume it with its recovery information after a connection failure or application restart.
Use the Standalone app for migration
Start and manage Mode Migration in the Standalone app. This feature is not available in the Libcodesk WebApp. Keep the app open while a transfer is running, and return to Settings > Mode Migration there to check progress or resume after an interruption.
How conflicts are handled
Libcodesk uses preserve, skip, and report when it cannot prove that a source record safely matches a destination record. Existing destination records and files are not blindly overwritten. Safe independent records continue, while each conflict is recorded for later review.
Do not create or edit large groups of records in either setup while its migration is active. Libcodesk prevents overlapping migration jobs and protects Cloud source data from changes during export.
Completion and validation
After transfer, Libcodesk rebuilds derived search data where required and checks processed counts and relationships. A job is shown as successful only after validation passes. If transfer finishes with conflicts, failed files, or validation differences, review the warning and download the report before using the destination as the primary setup.
Troubleshooting
- Unable to find the account: register or activate the Cloud administrator account using the registration link shown in the app, then sign in again.
- Organization unavailable: create/configure the Cloud organization and required libraries before retrying.
- Incompatible version: update the older setup; do not bypass the compatibility check.
- Connection interrupted: reopen Settings > Mode Migration and resume the incomplete job. Do not start a second job.
- Conflict reported: open the conflict list or report. Correct the destination/source data only after confirming which record is authoritative.
- File failed: verify storage access, file size, and free disk space, then resume. The source file remains unchanged.
Do and don’t
- Do confirm every library mapping before starting.
- Do keep the recovery information private.
- Do inspect warnings and the final report.
- Don’t delete source data after seeing transfer progress alone.
- Don’t manually copy the Cloud database into the Standalone database.
- Don’t guess when resolving identity or identifier conflicts.