> For the complete documentation index, see [llms.txt](https://olab4.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://olab4.gitbook.io/help/advanced-topics/import.md).
# Import/Export
The Import module works reasonably well in OLab4. It can handle zip files from OLab3 that have been saved in Medbiquitous Virtual Patient (MVP) format. If you do not know which format has been used -- the Importer should detect this automatically.
Generally, we have found that most maps play quite well after import and do not need too much editing. The same pathways, links, nodes, and general structure of the map will all be preserved and migrated without problem.
There are certain components that have been deprecated and so should be removed or replaced. See for notes on what is being removed in OLab4.
There is a challenge or two that becomes evident because the rendering component of OLab4.5 that displays the HTML text is much more stringent than the old version in OLab3. It will refuse to show pages with HTML errors, bad links and missing objects.
So, if you plan to migrate an OLab3 map to OLab4.5, here are some steps that will make the migration more successful:
To access the Importer, **login** to the OLab4 **Designer** and then look for the Import section at the top of the page:
```
https://designer.olab4.net
```
## Step-by-step: how to import OLab3 materials into OLab4
1. Create a zip file using the Labyrinths | Export Labyrinths menu in OLab3
1. For most cases, it is not crucial which format you select:
1. Medbiq MVP -- this is the more generic and widely accepted format
2. Advanced Export -- in OLab3 versions 3.3 and later, some function could not be supported by the MVP format so we developed the Advanced format. Try MVP first.
2. Copy the zip file to somewhere from where you can upload it to the new server (usually your laptop).
3. Login to OLab4 Designer at [https://designer.olab4.net](https://designer.olab4.net/)
1. with authoring privileges.
2. Generic or learner accounts cannot do this
3. You may need to request such an account on our Contact page.
4. Upload the zip file and import it
5. The importer will tell you if there are any errors or provide you with the new map ID number if successful.
6. You will need to reload the main list of maps to see your new creation
## Exceptions
There are few things that are **not** handled by the Importer:
* Avatars -- make a screenshot of these and convert them to images. See below
* Skins
* Clusters
* Rules
There are also some OLab3 capabilities that have been deprecated. You can see a list of them here:
{% embed url="" %}
### Why dump Avatars?
In the above section on Exceptions and things that have been deprecated from OLab3, we include Avatars.
"Oh, no, not the Avatars! I loved those wee cartoon figures." Yes, we know that OLab2 and OLab3 avatars are oddly popular as a feature. Even though they were very simplistic, many authors loved how you could use them to inject a personal face into the case.
So why are they gone?
OLab2 avatars were built on a neat little Adobe Flash tool. Many browsers no longer support Flash. Even in OLab3, we considered changing to HTML5 and a fully integrated system. However, while OLab3 Avatars are popular, we hit a limit on what we could do with them, unless we sank a lot of money into improving them. And there are now lots of other ways to create avatars that you can use in your OLab materials.
The Import tool does not handle Avatars at all. In fact, your Import will go smoother if you delete them from your OLab3 map before you export it. If you want to still use them, you can **simply save them as an image file** and then attach that to the OLab3 map in the Files section. Such images are easily imported.
### Other ways of creating Avatars
There are several other tools out there which you can use to create static and moving images. These can then be integrated into your materials.
* [Bitmoji](https://www.bitmoji.com/) -- easy to create with lots of existing themes
* idAvatars - unclear pricing model. Formerly CodeBaby
* [MovieStorm](https://www.moviestorm.co.uk/hub/purchase_edu) - we had fun with some of these but can get pricy
We do want to point out one small caution. We have found in the past that some authors spend a lot of time on creating attractive avatars. And they do make your cases appear more engaging initially. Good avatars have been rated well by students in software assessments in the past. But there is little evidence that they increase learning, which is a more important outcome.
## Export
Use the Export function to create a new zip that you can use to copy your map to another server.
Open the map that you wish to export in the OLab4 **Designer**. Then choose the menu item My Map | Export.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://olab4.gitbook.io/help/advanced-topics/import.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.