From apache + mysql 5.6 to centminmod

Ah i see you posted here instead.

For configuration nginx wise check out @Jimmy thread at IP.Board - IPB v4.1.x Files for setup config.

As to migration backing up your data files + databases via mysqldump to sql files and moving them to centmin mod server and creating nginx vhost via centmin.sh menu option 2 (Install - Quick Centmin Mod Install + Nginx Vhost Site + MySQL Database Setup) - and here's overview of config file structure for centmin mod Centmin Mod Configuration Files - CentminMod.com LEMP Nginx web stack for CentOS.

So you move your data files from Apache web root to Centmin Mod Nginx web root at /home/nginx/domains/yourdomain.com/public, edit nginx vhost if https ssl vhost at /usr/local/nginx/conf/conf.d/yourdomain.com.ssl.conf with IPB nginx rules and then import sql database backup created via mysqldump into Centmin Mod MariaDB MySQL. Edit IPB config to point to your new MariaDB MySQL database name.

I'd keep your apache/original server online for a few weeks even after centmin mod migration just in case you missed something the first migration attempt

Only way to migrate is to use a new server with fresh CentOS 7.5 64bit OS, install Centmin Mod 123.09beta01 (best performance) and then migrate your data over. There is no inplace switch from existing server Apache/MySQL to Centmin Mod.

 

For moving site data there's 2 general guides where the principles & steps of backing up and moving data is the same just slightly different for

1. Moving Centmin Mod site data to another Centmin Mod server
2. Moving cPanel/WHM site data to Centmin Mod server

Those guides move alot more than just the site(s) in question but config files etc. You can use your own best judgement as to the config files and whether you want to move them or just use the fresh server setup Centmin Mod config files as they get auto optimised for the server Centmin Mod initially installed on. These guides particularly the cPanel/WHM might give an better overview of where the data files and mysql databases go on Centmin Mod server.

 

Yes the link to whm/cpanel is just an example - the migration for any server is basically same - backup files + backup mysql databases to sql files and then move to centmin mod server and place them in the right locations which is still outlined in whm/cpanel linked guide

 

mysqldump backup databases is universal should work fine for mysql 5.6 mysqldump and import to mariadb 10.x

but yes need to reinstall CentOS but i wouldn't do it this way as you'd want to have reference to existing server during and after migration in case you missed moving some files or need to reference previous settings. Is this a dedicated server ? VPS ? Ideally you'd want to spin up a new server/vps for centmin mod install.

You can do a test run migration first spin up hourly billed digitalocean, vultr or linode VPS install centmin mod and do test migration of data from existing server to new vps without updating DNS.. do a few reload of hourly billed VPS and several test migrations and jot down all the steps you made until you perfect the migration process.

A few hours of hourly billed VPS only a few cent or a few days a couple of dollars. Then once you have a plan and steps perfected. Do live migration where you reinstall OS and reimport data. You can even use test hourly VPS installed Centmin Mod install to do a centmin mod to centmin mod migration then Upgrade - Nginx - Redis - Insight Guide - Centmin Mod Site Data Migration Guide

So you have a fool proof method of migration with practice backed process

Also would allow you to play with hourly billed test VPS with centmin mod without affecting live existing server first Even better is this will allow you to test both live existing site versus centmin mod powered test migrated data based site. Page speed and load testing etc and compare

 

basically

1. spin up hourly vps with enough disk space for your data with digitalocean, vultr or linode in same region location as existing dedicated server so faster transfers

2. install centmin mod 123.09beta01 on this hourly vps

3. backup data on existing dedicated server and move to hourly vps with centmin mod running and put in place data so your site is able to run on centmin mod vps but DO NOT update domain DNS so live site is unaffected

4. now you can test nginx rules/configuration on centmin mod vps and preview domain via private hosts file dns edit outlined here to make sure site data restored on test centmin mod vps is working as it should be and data is intact

5. now if you messed up on centmin mod test hourly VPS, easy just destroy that hourly VPS and try again - spin up another hourly VPS, install centmin mod and do steps 2 to 4 again until you perfect the progress and write down all your steps/cmds used

6. once perfected, you can do the actual real migration by backing up data to test hourly vps and then reinstall dedicated server OS and install centmin mod and then transfer backups form test hourly vps to dedicated server with centmin mod installed and re-apply the steps/cmds you perfected from practice runs

Then keep those steps/cmds and knowledge safe for future migrations

That's how I usually do migrations, never live migration the first time - always 1-3 test migrations to ensure all is well