Upgrading from Coda or Coda 2

Provided Nova was installed on the same Mac where Coda 2 was previously running, Nova will automatically import all of your sites and connection data at first launch. Coda sites configured with a local path will be set up as local projects in Nova whereas sites configured without a local path will appear as remote-only projects.

What if Coda 2 was installed on a different Mac?

If Nova was not installed on the same Mac that was previously running Coda 2, you can migrate your data via Panic Sync, but there are some things to consider.

Panic Sync will only sync your remote FTP, SFTP, WebDAV, and Amazon S3 connections. In Coda 2, server connections and sites were mostly the same thing. These have been decoupled a bit in Nova, as a local Nova project can now have multiple remote server destinations.

If you’re syncing your data from Coda 2 on a different Mac, these connections will be available in Nova’s Servers tab in Settings, ready to be used in new local and remote projects.

Important: Panic Sync does not sync projects or project files.

If you were previously using local project folders in this copy of Coda 2, you’ll need to manually move these project folders to the Mac running Nova and add them as existing projects in Nova’s launcher.

If these Coda 2 sites were remote-only projects, these will need to be re-added to Nova’s project launcher by way of clicking the Add Project button, selecting Add Remote Project, and selecting the server in question.

Can I use Coda 2 and Nova at the same time?

There’s no harm in using Nova and Coda 2 in tandem should you want to do that.

After importing your data into Nova for the first time, Nova won’t automatically import Coda 2 data from that point forward. You can re-run the Coda 2 import via Nova’s Help Menu if needed.

What about Coda 1?

Unfortunately, data cannot be synced or imported from Coda 1.x.

This article was last updated on October 27, 2022