Forums

Upgrade 5.6 to 5.7 basics

Permalink
OK, I'm missing something very basic.

I know that there are tools to assist with migration. I read the blog and have done migrations before.

But I'm not Concrete5 savvy enough to know how to take a Github repo and pull it in as an addon within Concrete5. How is that done?

Also, am I right in understanding that the 5.7 migration tool will be able to connect to my 5.6 site and migrate the data over? Or do I have to install the 5.6 software on my 5.6 site, export, and then use the 5.7 version to import?

I have a new 5.7 base build on a new server. I just need more complete steps on how to get the migration software installed and working and a better understanding of the work flow for moving things.

Thank you!
 
hutman replied on at Permalink Reply
hutman
What you will need to do is download the addon_migration_tool_legacy repo (use the Download Zip button), unzip it and put the migration_tool package in your 5.6 site. Go to the Extend Concrete5 page and Install the package.

Once you have done that you will want to download the addon_migration_tool repo (use the Download Zip button), unzip it and put the migration_tool package in your 5.7 site. Go to the Extend Concrete5 page and Install the package.

Then follow the steps as outlined in the YouTube video on the blog post. Links to all these things are in the original block post - here:https://www.concrete5.org/community/forums/customizing_c5/5.6-to-5.7...

One thing that is important to note is that you will need to have all the page types, attributes, and blocks already installed on the 5.7 site before you do the migration or things won't work properly. That is explained mostly in the video.
thanstra replied on at Permalink Reply
Perhaps I'm a bit dull, but where is the "Download ZIP button"?
hutman replied on at Permalink Reply 1 Attachment
hutman
See attached
thanstra replied on at Permalink Reply
I know how to download the repo. What I cannot get is the connection between Concrete5 and that set of files.

The files are on my local server, and unzipped. There is a directory there called "packages", I can step through the entire directory.

Now how do I have *concrete5* see that stuff? Do I pull it into Concrete5? If so, what are those steps?

When I go to addons in Concrete5, I see no way to get a local file or directory added in. That i what I'm missing right now.

Or is the tool completely separate? If so, how does my web server find it?
hutman replied on at Permalink Reply
hutman
You need to use FTP to put the unzipped migration_tool folder into the packages directory on your web server.
thanstra replied on at Permalink Reply
Well, we seem to possibly be getting closer.

My software is installed in /usr/localconcrete5. I find a couple of packages directories there:

./packages
./concrete/packages
./concrete/config/install/packages
./files/tmp/1348064103/concrete5.6.0.1/concrete/packages
./files/tmp/1348064103/concrete5.6.0.1/concrete/config/install/packages
./files/tmp/1337275345/concrete5.5.2.1/concrete/packages
./files/tmp/1337275345/concrete5.5.2.1/concrete/config/install/packages
./files/tmp/1438705838/concrete5.6.3.3/concrete/packages
./files/tmp/1438705838/concrete5.6.3.3/concrete/config/install/packages
./files/tmp/1411062495/concrete5.6.3.1_updater/concrete/packages
./files/tmp/1411062495/concrete5.6.3.1_updater/concrete/config/install/packages
./updates/concrete5.5.2.1/concrete/packages
./updates/concrete5.5.2.1/concrete/config/install/packages
./updates/concrete5.6.0.1/concrete/packages
./updates/concrete5.6.0.1/concrete/config/install/packages
./updates/concrete5.6.3.1_updater/concrete/packages
./updates/concrete5.6.3.1_updater/concrete/config/install/packages
./updates/concrete5.6.3.3/concrete/packages
./updates/concrete5.6.3.3/concrete/config/install/packages

I tried placing a copy fo addon_migration_tool_legacy in each of the first three directories. Concrete5 still does not seem to be finding that software.

Do I have to tell Concrete5 to look for and install it from there? How does it find the new package?

Is there a document which explains this in more detail?
hutman replied on at Permalink Reply
hutman
I don't have any documentation handy. You should put it in the first /packages directory. So the path should look like /packages/migration_tool/controller.php, then the Extend Concrete5 page should see that and put it in your list of packages awaiting installation.
thanstra replied on at Permalink Reply
I figured it out, but this could be a bit better documented overall.

The repository when unzipped has extra directories. It comes out as:

addon_migration_tool-master/packages/migration_tool

but, as you mention, the concrete5 packages directory needs it to start at migration_tool level.

Now, since I have you, when building the new site, is it better to start with an Empty Site or a Full Site? You mentioned that all page types, attributes, etc need to be there for the build. Will adding a Full Site help with that? Is there any way to check that everything is in place that I need before I test the import?

Thanks for your help and for being so responsive.
hutman replied on at Permalink Reply
hutman
It's up to you whether you start with a full site or an empty site. If you watch the video they tell you how you can see from the 5.7 interface what blocks/page types/etc. are missing from what you are trying to import.