Preferred workflow for exporting to Nisus Writer Pro

I’m trying to migrate a project into Nisus Writer Pro. I thought since both programms use .RTF, I could just drag and drop between them, but that doesn’t work.
Is there a way for exporting and importing the whole thing that leaves the chapter structure intact?

What do you mean when you say that you seek “… a way …that leaves the chapter structure intact…”? Do you mean one file (or folder) per chapter? If not, you could simply compile to an rtf file which as you say Nisus could import. That should leave the chapters as chapters, but not as separate files or folders.

I might just be missing a checkmark somewhere, but when I export to RTF and then import into NWP, the whole thing is one continuous text.

You seem to be missing a basic fact about Scrivener and Nisus Writer:

Scrivener projects are a “package”, even though they look like a file on your Mac. In that package, there may be hundreds, even thousands of files as each of the documents you see throughout the binder is a file within the package as well as a load of what one might call “administration files” keeping it all in order. Each of the documents and folders in your Draft/Manuscript folder is in fact an RTF file in the package. It is this format that makes Scrivener so powerful, as you can move elements around so easily.

When you compile your project in Scrivener, it produces a single RTF file, which is what Nisus uses as its native file format. But it is a single file, not a package, and so the contents appear as a single continuous document, as in any other word-processor.

By using the features available in Scrivener’s compiler, you can compile your project in such a way that each heading, subheading etc. is in a different format — size, colour, style — that you can use NWP’s extremely powerful search and replace to turn into appropriate heading styles for your final output, thus preserving the outline structure represented in Scrivener’s binder.

Mr X

Yes. And is there a preferred way to go about doing this…?

It would be worth your while having a look at some of the tutorial videos on compiling on this page: - for example (scrolling down), Introduction to Compile, and Compiling a Structured Outline. Also, unless you’ve already been through the Interactive Tutorial (under the Help Menu in Scrivener), you’d find it helpful to you to do so: compiling is a fundamental part of Scrivener, because, instead of adjusting your formatting and layouts as you go along, as you do in most word processors, such as Microsoft Word, you can do it at the end, in the compiling process.