Rather than upgrade our 1.6.9 EE install to 2.X, we’re planning on purchasing a second license for 2.X rather than upgrading, and then developing new sites in 2, while maintaining a couple of older sites in 1.6.X. 

That’s fine, but there are a couple of sites we do want to migrate to the new version.  There are some sensible Org level reasons for this, but it ended up being a headache on the ground. 

How do I go about essentially exporting a site (templates, categories, channels/weblogs, entries) from 1.6.9 to 2.X without doing an upgrade so we can keep the 1.6.9 install as it is?

Thanks,

-Ben

Hi, Ben -

You can’t do what you’re describing.

What you *can* do is duplicate your database and files and get a second installation going, then upgrade that to EE 2.

That’s disappointing - though thank you for the candid answer.

Are there any differences in an upgraded version of 1.6.9 -> 2.x VS a clean install of 2.X?  For example, any artifacts of 1.6.9 which hold over in an upgrade, which might be troublesome down the line somewhere?

Thanks,

-Ben

There should not be any artifacts, if there were that’d be a bug.

But the 2.x database is significantly different than the 1.x database - the updater converts that database information for EE 2, which is why you must run the updater.