Upgrading Joomla from 3.10 to 4.49

I'm having trouble so far with AJAX Loading Error: error updating Joomla 3.10 to 4.4.9.  I have given up.  I decide to install Joomla 4.4.9 in a separate folder and move CB Sub over.  Is there a way for me to move the config, users, and subscription over to the new site?

Thanks.
Michael Phan

I'm having trouble so far with AJAX Loading Error: error updating Joomla 3.10 to 4.4.9.

Can you describe what you mean by this? Have you followed the migration guide below?

docs.joomla.org/Joomla_3.x_to_4.x_Step_by_Step_Migration

Sounds like you maybe just running out of system memory. You should be able to increase that in your servers PHP ini file. Contact your host if you're unsure how to change that.

You can also download the upgrade package from 3.x to 4.x below. Then try using it instead of having it download through the update tool.

downloads.joomla.org/cms/joomla4/4-4-10

Is there a way for me to move the config, users, and subscription over to the new site?

This is complicated to do manually, but yes it's doable.

First ensure CB and all your CB plugins on your Joomla 3 install are up to date. Then migrate it to Joomla 4. Next export the following database tables and import them into your new site. Note skipping the Joomla 4 migration step might be database table data could be incompatible, but you might be able to just run Joomla's database checker tool on your new install and it could be fine.

All tables beginning with the following:
_comprofiler
_cbsubs
_groupjive

Now you need to move your users and in Joomla this requires a few tables:
_users
_user_keys
_user_mfa
_user_notes
_user_profiles

Now you need to be sure your ACL is moved, which is your view access levels, usergroups, and their assignments:
_user_usergroup_map
_usergroups
_viewlevels

I already tried increasing the php.ini memory and same error pops up.  That's why i might have to go the manual way

Hmm, some other tricks I've seen is to remove the .htaccess file in Joomla root and if one exists in /administrator also remove it. Next disable all 3rd party extensions so they won't load during the migration. Finally you may need to increase max_execution_time as it's possible PHP is just timing out during the migration.

Aside from that I'm not sure what more to recommend. Our migration went rather smoothly, but we basically only use our products + Kunena.