How to import a SCORM file into Articulate Storyline?

Hi, Exactly the same case. I suppose we can´t import SCORM packadge but only the source data in *.story format. But I am looking for the way how to do it now...

Is there a feature to embed a SCORM in a project then? So that the project is now hosting the old SCORM file?

Hi Manh,

Welcome to the E-Learning Heroes community! 

You should still have access to view the project that was uploaded to the LMS. In order to edit a Storyline project, you will need the original .story file. If your team member saved the project to their local hard drive, we will not have access to it. 

If a course was created in Rise 360, you have the option to transfer the ownership of the content. Here's a resource that explains how to manage content when users leave your team.

Please don't hesitate to reach out to our team through a support case if you need further assistance with a project. We'll be happy to help!

Hi Isolde,

Thank you for reaching out!

Currently, you need the original .story file to edit your course. I understand how frustrating this can be when you have instructional designers who have left with these files. We appreciate your feedback and love hearing from our customers about what features will be beneficial to them. 

This capability isn't on our current feature roadmap, but if it does make it on, we'll be sure to update this discussion.

Has there been any progress on this? I have hundreds of courses that I want to edit with 360 and publish to a new LMS. I have all the source files but they weren't created with Articulate. 

Not being able to bring SCORM files into storyline is actually something that  makes it very difficult to ever make the switch to storyline if you have designed things in other applications.  You have SCORM outputs from your designs in those, but you're stuck with them as-is.

I am facing that right now, where I literally just built something 5 months ago, and now need to update, but had made the switch to storyline and cannot edit my files.  Instead I am literally re-creating the work product which is a total waste of my time and very frustrating. 

I am facing that right now, where I literally just built something 5 months ago, and now need to update, but had made the switch to storyline and cannot edit my files. Instead I am literally recreating the work product which is a total waste of my time and very frustrating. 

why do you not backup your original .story files?

Scorm is the final output. Similar to a print on paper....if you keep the original Word of .doc you can edit it... i seldom see the question can i generate a Word from my print... thats the same thing as creating a .story from scorm.

Always save and keep track of your .story files. Those are your source. If someone leaves a company he is obliged to make sure those sources are available for his successor. If not im quite sure you can take legal action and sue him/her to deliver those sources.

If you switch to another tool... you might run into the issue that you have to remake your courses. The Scorms you can always upload to any other LMS, but changing things in another authoring tool is impossible.

If you want/need a format thats open to edit in most tools, you should go for HTML5, you can edit HTML5 in Notepad and any editor outthere. As is the HTML5 output Storyline creates is not 100% compatible with standard HTML5. A lot is coded in a specific Articulate way and thus hard to decipher. You however can edit in the published HTML.

I hear a lot of people here asking, “I baked a batch of cookies, and nobody ate them. Why can’t I drop them into a mixer, beat them up, add some peppermint to the dough, and rebake them?” That, after all, is the same as taking SCORM and dropping it into SL, just that one uses a computer, and the other a mixer.  To be fair, if you were an awesome programmer and had sufficient motivation, you could probably create a program to decompile SCORM. You could possibly end up with something. Of course, given the demand, you would be working for cents per year.  In the same way, if you beat the cookies into a fine enough powder, and add milk, you might end up with something.

Perhaps this little analogy will help explain why decompiling SCORM (or any published SL format) isn’t done.

the following elements can you can easily extract from a scorm package (or a "publish to web" package)

unzip the package, you will find ...

• video (mp4)* (-> ./story_content/... )
• audio (mp3)* (-> ./story_content/... )
• images (jpg, png, gif)* (-> ./mobile/... )
• resources (-> ./story_content/external_files/...)
• web object (-> ./story_content/WebObjects/.../...)

* but the original filenames are gone