I've been working on a horrible EE1 installation and bring it into EE2. Unfortunately it was one of those sites that decided to use Gypsy, oh and Structure and just to make things interesting, MX Uni Editor's file field.

The upgrade went relatively smoothly actually, although Gypsy was used throughout there were only a handful of channels so was able to just have 1 field group in the EE2 site and share it amongst channels.

The Structure upgrade went smoothly also.

Where we fell down was the assignment of images and attachments to entries.

1 Answer 1


We created an XML feed of all channels (we couldn't automatically export because http://devot-ee.com/add-ons/weblog-entries-exporter doesn't support Gypsy).

We then used Datagrab to import the XML feeds respectively. Datagrab did a great job of mapping the Matrix rows of MX Uni Editor file fields to Assets 2 fields on 'news' and 'press release'. However, when we did the same thing for the 'page' channel that Structure uses as a general page type, it would blow out the Structure settings.

The simple way around this for us was to temporarily change the 'page' channel to an asset type in the Structure settings, run the import, confirm the images/attachments were properly assigned and then revert that channel back to being a page.

It took a few attempts before we realised the import was screwing the parent Structure entries.

  • I've used the 'Undo Gypsy' migration tool successfully quite a few times. And all addons that are not EE2 compatible I either convert to text first, or change to EE2 compatible addon. We updated 'Undo Gypsy' a while back to tackle Matrix fields too: github.com/litzinger/UndoGypsy.eeaddon Commented Jul 29, 2013 at 6:17
  • Thanks Brendan. Quick question re Undo Gypsy. Where you map weblogs/channels to field group id like gist.github.com/stevieg83/6131920 am I right in saying that the first number in that array is the weblog/channel id and the second is the newly created field group id? Commented Aug 1, 2013 at 14:31
  • Yep, that's correct. If you have nGen File Field used though, do the conversion of those first. Commented Aug 1, 2013 at 23:56
  • Cheers, yeah seems I'm in a little bit of a jam. I've got a weblog called 'static' which has its own field group as well as pulling in other fields from other channels. Its own field group also extends other channels so when I run the script, it transfers the other channel fields but not its own. Pretty funky :-( Commented Aug 2, 2013 at 10:04
  • That sort of sounds like it's doing what it's meant to do. If you chose to use a different channel field group rather than the original, it would transfer and copy all fields into it I guess. It's certainly not a silver bullet, but it's still pretty good. Commented Aug 5, 2013 at 1:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.