Migration Remap
Migration Remap helps an organization administrator compare a completed previous-database migration with its original source and approve selected field corrections. It is not a second migration, a library reset, or an automatic replacement of current records.
Before you start
- Sign in as the organization administrator and select the correct migrated library.
- Keep the unchanged previous database and your recovery backup.
- Check that the library has a completed migration history. A library without that history cannot use Remap to change unrelated records.
- For a Cloud setup, select the completed transfer that brought the migrated records into that library.
- To prepare an analysis file for a Cloud setup, retain the Local setup that completed the original migration, including its migration history. The unchanged previous database alone is not enough to establish which current records belong to that migration.
- Keep prepared analysis files private: they can contain library information. The Libcodesk WebApp accepts the prepared analysis file, not an encrypted previous database.
Screenshot to add: Migration Remap with the library, source selection, and completed transfer on desktop and a narrow screen.
Prepare and review in the Standalone app
- Open the Standalone app for Windows in the Local setup that completed the migration.
- Sign in as its organization administrator, select the migrated library, and open Advanced Manager > Migration Remap.
- Select Select original previous database and choose the unchanged database used for that migration.
- Wait for source preparation to finish. Check the selected file name, then review the source field mappings.
- Keep the suggested mappings, or explicitly choose another available source column for a supported text field. Contact and date values keep their prepared conversions; record identities cannot be changed here.
- Select Analyze selected mappings to review corrections in that Local setup. Analysis alone does not save corrections.
- If you need to review the transferred records in a Cloud setup, select Save analysis file for Cloud setup and choose a new private file location. The Cloud review has its own mapping selection and approval; saving this file does not change Cloud records.
The selected database is used as a read-only source. Do not modify it or run the original migration again to prepare this review. If the Local setup or its completed migration history is unavailable, stop and ask the organization administrator for the retained migrated setup. The browser cannot reconstruct that history from an encrypted database alone.
Screenshot to add: Standalone app showing original database selection, source mappings, analysis progress, and the analysis-file save action.
Review a Cloud setup
- Open Advanced Manager > Migration Remap.
- In the Libcodesk WebApp, select the matching completed cloud transfer.
- Select the prepared Remap analysis file.
- Review Source field mappings. Keep the suggested mappings or choose a different source column for a supported text field.
- Select Analyze selected mappings. Keep the workspace open while the progress count updates. Analysis does not replace current library records.
The same prepared-file workflow is available when the Standalone app is connected to a Cloud setup. Original previous-database selection is a Windows Local-setup preparation step, not a direct encrypted-database upload in the browser.
Date and structured values retain their prepared conversions; do not rename a source column to force an unsupported conversion. If the suggested conversion is wrong, stop and ask your organization administrator to review the source.
Review differences
The review table shows the record, field, source value, current value, proposed value, and review status. Use the category filters and pagination to work through large results without opening everything at once.
- Already matches: no correction is needed.
- Earlier value unknown: the earlier imported value cannot be established. Review carefully; an unknown earlier value is not proof that the current value is wrong.
- Source correction: a supported difference is available for review.
- Changed after migration: a later edit may be intentional. Remap protects that edit and does not offer it for replacement.
- Record missing or Blocked: the correction cannot be applied safely through this review. Do not run replacement migration as a shortcut.
- Applied: the selected correction was already completed.
Nothing is selected automatically. Select only the individual field corrections you approve. Selections are preserved when you change pages, and each preview is limited to 100 corrections. Other fields and unrelated records remain unchanged.
Screenshot to add: Field review showing source, current, proposed, and a later-edit warning, including Arabic right-to-left layout.
Approve corrections
- Select Preview selected.
- Read the exact corrections in the preview. Do not approve a field merely to remove a warning.
- Type the displayed confirmation code.
- Select Apply approved corrections and wait for the result.
- Open a few corrected records and check their visible values.
If a record changes after the preview, Libcodesk refuses the outdated approval. Refresh the results, review the current values, and create a new preview. Do not repeatedly submit the old confirmation.
Export the report
Select Export review report to save the review and results. Keep the report securely with the upgrade records. It may contain library information and should not be attached to a public support message without review.
When the browser offers a save-location dialog, choose the destination first; pages are written progressively while the checked-record count updates. Browsers without that save capability can download only a bounded-size report. If a large report exceeds that limit, use the Standalone app or a browser that offers the save-location dialog; no partial report is presented as complete. If the review changes during export, refresh it and export again.
Troubleshooting
There is no completed migration history
Check that you selected the right library. For a Cloud setup, check the completed transfer. Remap cannot infer ownership from matching names or identifiers alone. Contact your organization administrator if the expected history is missing.
The prepared file is rejected
Prepare a new Remap analysis file from the unchanged previous database. Do not upload the database itself or edit the prepared file by hand.
I have the old database but not the migrated Local setup
Ask the organization administrator for the retained migrated setup and its history. A matching file name, member name, or accession number alone does not prove that a current record came from that migration. Do not create a fresh replacement migration to bypass this requirement.
Analysis was interrupted
Current records are not automatically replaced by analysis. Refresh the workspace and review its reported state before trying again. If a correction was already applied, confirm that status before selecting it again.
A field or relationship is blocked
Leave the current value unchanged and review the report. Missing records, unsupported fields, ambiguous matches, and protected relationships require a separate reviewed correction; Remap does not guess or rebuild the entire migration.
Do and don't
- Do check the library and original source before starting.
- Do preserve later edits that are still correct.
- Do review one field at a time and keep the result report privately.
- Don't treat an unknown earlier value as approval to overwrite.
- Don't change internal record identities or use full replacement migration to clear Remap warnings.
- Don't edit or publicly share the prepared source file.
FAQ
Will Remap run the migration again?
No. It reviews selected field corrections for records linked to the completed migration. It does not reset the library or create a second set of migrated records.
Can another librarian's later changes be kept?
Yes. Leave those fields unselected. A later edit is shown for explicit review and is not silently replaced.
Can I select all hidden results?
No. Select individual fields and review the exact preview. This avoids accidentally approving unseen corrections.