Overview of Content Migration in Thrive

This article provides an overview of how content can be migrated from your legacy learning management system (LMS) into Thrive. It outlines which content types are supported, key considerations when preparing your files, and what to expect from the migration process.

Note:

With a Pro+ subscription or a one-time paid service, you can get support to seamlessly transfer content from your legacy LMS to Thrive.

What Can Be Migrated?

The migration process allows the importing of these content types:

• E-learning files - SCORM 1.2, TinCan (xAPI), CMI5, SCORM 2004

• Word processor files - .pdf

• Video files - .mp4, .mpg, .wmv, or avi

• Image files - .png, .jpg, .gif, .svg

• Links (URLs)

• Articles (txt/html content)

Content Request

There is a mechanism to import the files and links into Thrive with the associated metadata.

To achieve this we would need the vendor to provide:

• the supported e-learning packages as .zip files.

• other supported files (pdfs, videos or images).

• the URLs of any ‘link’ content types.

• the thumbnail of the content.

• the associated metadata for each content type.

The metadata required alongside the content would be:

• Unique reference ID -  a unique reference for the item, usually the ID from origin.

• File name - file/elearning/video extension used to determine the type. If URL, just url is required.

• Content Title (3 - 100 characters) - the name/title of the content.

• Description (Up to 1000 characters) - the description/summary detailing the content.

• Author (email or identifier) - usually set to a temporary import account.

Optional additional metadata:

• Published Date (DD/MM/YYYY ) - if required, the creation date of the content.

• Content thumbnail - the thumbnail you want associated with the content.

• Language - the ISO 639 language code, if applicable.

• Collaboration - adding the content to a specific collaboration in Thrive.

• Content Visibility - whether the content should be public or private.

• Tags - what do you want the content item to be tagged with - if multiple tags required separate by a comma in the cell. Tags will need to already exist on the platform.

• Audience - Is there a particular audience that the content needs to be shared with. This will need the audience ID.

• Endorsed - Do you want the content to be endorsed.

The file name of the content is essential so it can be used as the ID between the file and the metadata during import.

Example expected metadata file:

If the same content is in multiple languages, a separate record within the metadata file would be required.

We recommend requesting a full database extract ensuring it covers both the content and associated metadata as outlined above.

End to end this process can take 4 - 5 weeks. During this time we would initially import into your staging site for testing before moving to production.

Considerations

• Do you want all the content to be imported as public or private?

• Do you want all content to be published by a collaborator, or the author specified in the metadata file. If by a collaborator, which collaboration group do you want to import all content into?

Client Actions following Migration

Once the files have been moved over to your Thrive platform you may need to perform the following tasks if not included in the metadata:

• Tag the content with relevant tags if not done so as part of the import

• Update collaborations if necessary

• Endorse content where needed

• Restrict private content to certain audiences where applicable

• Create pathways containing the migrated content if required

How to share the files with Thrive

Thrive will set up an SFTP server for you and your legacy vendor to upload the content files and associated metadata for migration.

To complete the setup, we will need an SSH key for secure access. Please share the public key with us, which you may need to obtain with support from your IT team. They or your legacy vendor can also assist you in accessing the SFTP server and uploading the files.

Note:

If your IT team needs support creating an SSH key see the below.

SFTP SSH key Creation

For Windows Users

Method 1: Using Windows' Built-in OpenSSH

Prerequisites: Windows 10 or later with OpenSSH installed (usually pre-installed).

1. Open PowerShell:

   • Press Win + X and select Windows PowerShell or Windows Terminal.

2. Generate the SSH Key Pair:
   ssh-keygen -t rsa -b 4096 -C "your_email@example.com"

   • Options Explained:

     • -t rsa: Specifies the RSA algorithm.

     • -b 4096: Sets the key length to 4096 bits for enhanced security.

     • -C: Adds a comment (usually your email) for identification.

3. Follow the Prompts:

   • Save Location: Press Enter to accept the default path (C:\Users\YourUsername\.ssh\id_rsa) or specify a different location.

   • Passphrase: (Optional) Enter a secure passphrase for additional security or press Enter to skip.

4. Locate Your Keys:

   • Private Key: C:\Users\YourUsername\.ssh\id_rsa

   • Public Key: C:\Users\YourUsername\.ssh\id_rsa.pub

Method 2: Using PuTTYgen

Prerequisites: Download and install PuTTY.

1. Open PuTTYgen:

   • Launch PuTTYgen from the Start menu.

2. Generate the Key Pair:

   • Parameters:

     • Type of key to generate: Select RSA (or Ed25519 for newer systems).

     • Number of bits: Enter 4096 for RSA.

   • Click Generate and move your mouse within the window to create randomness.

3. Save the Keys:

   • Private Key: Click Save private key and store it securely (e.g., id_rsa.ppk).

   • Public Key: Click Save public key or copy the text from the Public key for pasting section.

4. Convert to OpenSSH Format (If Needed):

   • In PuTTYgen, go to Conversions > Export OpenSSH key to save the private key in OpenSSH format (id_rsa).

For macOS Users

Using Terminal with ssh-keygen

Prerequisites: macOS with Terminal access.

1. Open Terminal:

   • Navigate to Applications > Utilities > Terminal or use Spotlight (Cmd + Space) and type Terminal.

2. Generate the SSH Key Pair:
   
   ssh-keygen -t rsa -b 4096 -C "your_email@example.com"

   • Options Explained:

     • -t rsa: Specifies the RSA algorithm.

     • -b 4096: Sets the key length to 4096 bits for enhanced security.

     • -C: Adds a comment (usually your email) for identification.

3. Follow the Prompts:

   • Save Location: Press Enter to accept the default path (/Users/YourUsername/.ssh/id_rsa) or specify a different location.

   • Passphrase: (Optional) Enter a secure passphrase for additional security or press Enter to skip.

4. Locate Your Keys:

   • Private Key: /Users/YourUsername/.ssh/id_rsa

   • Public Key: /Users/YourUsername/.ssh/id_rsa.pub

To enable your access to our SFTP server we require the Public Key that you have just created. We will create a user and assign them the public key and it is with this user that you can connect and upload to our SFTP server.

Configure Your SFTP Client

After generating and uploading your SSH keys, configure your SFTP client (e.g., FileZilla, WinSCP, Cyberduck) to use the private key for authentication:

1. Open Your SFTP Client Settings:

   • Navigate to the connection or authentication settings

2. Specify the Private Key:

   • Point the client to your private key file (id_rsa on macOS or id_rsa.ppk on Windows if using PuTTY).

3. Connect to the SFTP Server:

   • Use your username and the configured private key to establish a secure connection.

   • Enter the connection details Thrive has shared with you, e.g.

SFTP: xxx-sftp.learn.link

Username: [To be shared]

Port: 22

Logon Type: Key File

Next Steps

If you're ready to begin migrating your content, see our Step-by-Step Guide to Migrating Your Content to Thrive for detailed implementation instructions.