The Configuration Migration tool is designed to streamline the process of transferring configurations between tenants. However, users may encounter errors or warnings during migration. This troubleshooting guide is intended to help you understand and resolve these common issues.
General Errors:
General Import Error
- Error Message: "X cannot be imported. Unable to create file for template, the export file may have expired."
- Resolution: Ensure the migration file is recent as it expires seven days after export. Best practice is to export the file from the source tenant at the time of migration.
Import Errors on Schemas:
Duplicate Warehouse Name
- Error Message: "Another field of this schema has a similar name with the same warehouse column name. Please try another name."
- Resolution: Update the warehouse name for conflicting fields, then re-export and continue the migration.
Archiving Field in Name Template or Constraint
- Error Message: "Cannot archive field that is used in a name template or constraint."
- Resolution: Manually remove the field from the name template/constraint in the destination or unarchive the field on the source, then re-export and continue.
Changing DropdownId on Field with Data
- Error Message: "Schema field 'X' cannot change dropdownId on a field that contains data."
- Resolution: Do not update a dropdown field to map to a new dropdown after data has been recorded. Instead, create a new result field or use the existing dropdown.
Adding Required Field Post-Data
- Error Message: "Cannot add a required field once data has been received."
- Resolution: Avoid making a field required after data capture. Opt for a new result field or use the existing dropdown as is.
Updating with Associated Schema Tags
- Error Message: "X can be imported with changes. Option Y has 188 associated schema values."
- Resolution: Acknowledge the warning. If comfortable updating these field values to the new Option Y, then proceed.
Import Errors on Templates or Sub-Templates:
@-Mentions and Internal Links
- Error Message: "Template X can be imported with changes. Replacing reference to Internal Link 'XXX' with a placeholder."
- Resolution: Delete @-mentions or replace them post-migration.
Dependency on Archived Entity Schema
- Error Message: "Template X cannot be imported. It depends on entity schema 'Y', which is archived."
- Resolution: Unarchive entity schema 'Y' on the source tenant or remove it from the template, then re-export.
Dependency on Archived Schema Field
- Error Message: "Template X cannot be imported. It depends on field 'Z' of entity schema 'Y', which is archived."
- Resolution: Unarchive schema field 'Z' or remove it from the template, then re-export.
Dependency on Ignored Entity Schema or Field
- Error Message: "X cannot be imported. It depends on entity schema 'Y', which is ignored. It depends on field 'Z' of entity schema 'Y', which is ignored."
- Resolution: In the schema listing, choose to create or update entity schema 'Y', or remove references to it in the template, then re-export.
Missing Dropdown Options
- Error Message: "X cannot be imported. It depends on option 'Y' of dropdown 'Z' which is missing from the import file."
- Resolution: Re-select pre-filled dropdown options in the structured tables of the template, then re-export.
We will continue to update this article to provide a more detailed guide. Always ensure to check the latest version of Benchling's documentation or reach out to our support team for any unresolved issues or complex scenarios.