Finished a manual import utility for Ghost tonight. Should be able to use it as a starting point for future integrations.

This will be extremely useful for getting new users on board right away, so we don't want to charge for it. It's also not necessary for already-launched 2.0 / #collections_sprint

Commenting here since this affects all the child tasks:

What should happen if a user imports a blog with a name that already exists in the database? For example, a user has a WriteFreely blog called "My Thoughts" (with the slug my-thoughts). They then import posts from an old WordPress blog that's also called "My Thoughts". WriteFreely won't allow two blogs with the same name (I checked). How should we handle the collision?

Options that occur to me:

• Create a second blog called "My Thoughts 2" with the slug my-thoughts-2. (Continue incrementing to my-thoughts-3 if my-thoughts-2 is already taken, etc.)
• Add the posts from the imported blog to the existing blog, effectively merging the imported and existing blogs.
• Offer the user the ability to rename the imported blog as part of the import process.

Also worth considering: offering the user the choice of these options. But to get the project rolling, let's establish a default first and work up from there.

I'd say the default behavior should be #1, to generate a unique slug for the imported collection.

We already do this with post slugs by appending 4 random characters in case of a collision, and I'd say we do the same here. That'll save work parsing the last number, handling errors, etc. As a bonus to this behavior, the user can always then move their posts to the collection with the original name if they want.

In the future, I agree the user should have a choice (probably in line with T614: WriteFreely import blog selector). But definitely out of scope for now.

Will do.