Migrating a DS Lab Model via Git
The Model Migration feature simplifies collaboration by allowing you to export a Data Science Lab (DSL) model to a Git repository and import it into a different tenant or account. This process avoids duplication, ensures consistency, and helps you maintain a clear version history, ultimately accelerating teamwork and streamlining workflows across different environments.
Pre-requisites for Migration
Before migrating any DSL script or model, complete the DS Lab Migration configuration in the Admin module, including:
Version Control Settings
Execution Settings
DS Lab Settings
Export a DSL Model (to Git)
Use this to migrate a model from your current space to Git so it can be imported elsewhere.
Navigation path: Data Science Lab (DS Lab) > Models > Model Migration
Steps
Open the Models list from the DS Lab module.
Select a model from the list.
Click on the selected model to get the actions drawer for the model.
Click the Model Migration icon for that model.
The Export to GIT dialog opens.
Enter a Commit Message.
Click Yes to confirm.
A notification confirms the model has been exported (migrated) to Git.
Import a DSL Model (from Git)
Navigation path: Admin Module > Git Migration > Import File > Import Document > Migration – Document Import
Navigate to the Admin Module.
Click the Git Migration icon from the side navigation bar.
Click Import File.
On the Import Document page, click Import.
The Document Import page opens.
Select New VCS for the Version Control configuration.
From the Select Module drop-down menu, choose Dslabs.
From the Migration – Document Import drop-down menu, select Models.
Use the Search bar to locate the specific model to import.
Click the model from the displayed list to select it.
The available versions of the selected model appear on the right side of the page.
Select the desired version by checking the corresponding checkbox.
Click Migrate.
A notification message confirms that the model has been successfully migrated.
Accessing the Migrated Model
Open the Data Science Lab module.
Navigate to the Models list page within the project.
The migrated model will appear in the list, ready for use in notebooks or pipelines.
Behavior & Limitations
Spaces: Import must target a different space (or different tenant).
Project Transfer: The associated DSL project is transferred along with the model.
Same-Space Transfers: Not supported—use a different space or tenant.
Auditability: Commit messages and Git history serve as the audit trail of model evolution.
Troubleshooting & Tips
Migration option unavailable: Verify Admin → DS Lab Migration is configured.
Import list empty: Confirm the model was exported successfully, and you’re in the correct target space/tenant. Use the Search bar with the exact model name.
Permission errors: Ensure you have the required Admin/DS Lab privileges in both source and target environments.
Version ambiguity: Prefer the latest stable version tag or use descriptive commit messages to avoid importing unintended versions.
Linked assets: If the model expects specific external libraries or data paths, validate environment parity after import.
Last updated