Watch a collection of short and easy to understand how-to video tutorials to quickly get up and running with NVivo for Mac.
I spent several months researching the options, and ultimately decided to trial MAXQDA. We brought in a MAXQDA certified trainer, and bought a network license so that our large team at Microsoft could use the tool. We were not disappointed. I was so convinced in its efficacy in the applied qualitative field that I bought MAXQDA for my team when I joined Amazon. I was especially delighted when they recently added the Stats package, which allows us to avoid the extra expense of buying SPSS. I use MAXQDA almost daily, and am the first to recommend it to applied research teams.
Sam Ladner, PhD, Senior UX Researcher, Amazon.
NVivo 10 for Mac projects have a different file format from those created in NVivo 10 for Windows:. NVivo 10 for Mac (.nvpx). NVivo 10 for Windows (.nvp) You cannot open an NVivo 10 for Windows project (.nvp) in your NVivo 10 for Mac software—you will need to convert it to the NVivo 10 for Mac format first. You can do this using the 'copy project' feature in NVivo 10 for Windows (Service Pack 5 or later).
You can also export selected items to a new NVivo 10 for Mac project. For detailed information on converting projects into the Mac format (by copying or exporting) refer to the.
You can open an NVivo 10 for Mac project (.nvpx) in NVivo 10 for Windows (Service Pack 5 or later) and it will be converted into the NVivo 10 for Windows format for you. You can also import the content from an NVivo for Mac project into an NVivo for Windows project. Alternatively, you can use the 'copy project' feature in NVivo 10 for Windows (Service Pack 5 or later) to copy a project from one file format to the other. The initial releases of NVivo 10 for Mac have a subset of the features available on NVivo 10 for Windows. If you convert your NVivo 10 for Windows project and access it on the Mac, you may not be able to work with all your project items. WARNING If a source in the original NVivo for Windows project contained 'see also' links, then do not edit the source in NVivo for Mac—otherwise, all 'see also' links in the source will be permanently deleted. Always ensure you are on the latest version of the software—future versions may address this limitation.
Can I work with a project on Windows and Mac? It is possible to work with a project on both Windows and Mac (cross-platform), however, we recommend that you work with your project on a single platform due to some known limitations and issues. Refer to for more information. Can we work as a team with some users on Windows and others on Mac?
We recommend that all team members use the same version of the software (and do not work cross-platform). This release of NVivo for Mac provides limited.
If you need to work with others in a shared project, you should consider using NVivo 10 for Windows. Refer to for more information on known limitations and issues. Cross-platform limitations and issues There are some known limitations that you should consider before working on a project cross-platform:. The initial releases of NVivo 10 for Mac have a subset of the features available on the NVivo 10 for Windows platform. If you convert your NVivo 10 for Windows project and access it on the Mac, you may not be able to work with all your project items.
Many of the teamwork features that are available in NVivo 10 for Windows are not available in NVivo 10 for Mac—for example, the ability to merge projects, run coding comparison queries or view coding stripes by user. If a source in the original NVivo for Windows project contained 'see also' links, then editing the source in NVivo for Mac will cause the 'see also' links to be permanently deleted. There may be slight differences between NVivo for Windows and NVivo for Mac in the coding coverage percentages displayed. This is due to differences in the handling of blank spaces when calculating coding coverage. File links must be updated each time you convert a project—refer to for more information.
Some queries created in NVivo for Windows will not run in a converted project in NVivo for Mac. For more information, refer to. Project conversion can take a long time depending on the number of documents and PDFs and the amount of coding. We are working on compatible project file formats in the future that will not require conversion. In addition, you may experience the following issues when working with projects cross-platform:.
A corrupt PDF file (that is, a PDF file that could not be opened with Adobe Reader) was successfully imported and coded in an NVivo for Windows project. However, the PDF could not be opened in a project converted to NVivo for Mac format.
Certain documents in an NVivo for Mac project failed to convert when the project was converted to NVivo for Windows format. These documents also could not be exported from NVivo for Mac to.doc or.docx format. If you code documents that contain embedded images or complex tables in NVivo for Mac, and then open the project in NVivo for Windows, you may experience problems when you open the node. You can avoid these problems by converting documents with embedded images or complex tables into PDF files before importing them into your project. Executing multiple project conversions during the same session can slow the conversion process or cause the conversion to fail.
Rebooting the computer between project conversion can improve performance If you decide to work with a project cross-platform, knowing these limitations, we recommend that you import all sources into the Windows project. Furthermore, if you are working in a team, the Windows project must be the 'master project' because the Windows version of the software has the full feature set, including the ability to merge content from other projects. Always ensure you are on the latest version of the software—future versions may address many of these limitations. Why does my converted Windows project look different on Mac?
When you open a converted project in NVivo for Mac, items that are not supported on the Mac version of the software are hidden.