manager not working after transfer

I would try to get it working before upgrading. Try deleting all files in the core/cache directory and clearing your browser cache and cookies before trying to log in.

If that doesn't work, check the other paths and URLs in the config file. They should all end with a trailing slash.

If you're still stuck, go into the db in PhpMyAdmin and turn off the compress_js and compress_css System Settings in the modx_system_settings table.

This may be a bit late, but I find it much simpler to install a fresh copy of MODx on the new server, then use Vapor to make a package of the original and install it in the new MODx.

Follow the first 3 sets of steps in the Vapor documentation to install and run Vapor on your original site, then (ignoring the import section) download the core/packages/your-site-package.zip that Vapor generates, upload it to your new core/packages, and install via Package Manager using the "Search Locally for Packages" option.

after upgrading cleaning everything manager still doesn't load. Is it possible from technical standpoint to clear all files (apart from assets) and install a completely new instance(same modx version 2.2.0) but load the old database?.

@sottwell - yes, I thought of that yesterday but I don't have access to the old server.

Try it out on a localhost installation first, but it should work. As long as the three config.core.php files and the core/config/config.inc.php file all have the correct paths and links. Only the core/cache, core/components and core/packages should have different stuff in them, and you can empty the core/cache directory anyway.

ok, seems to work. I've installed an exact copy laded the db. No problems so far a part from furl's but I don't think it will be a problem. Thank you very much for your help! Definitely will try vapor next time.