Move 2.2.1 set from subfolder to replace 1.5.5 cart version in public_html

I have a live 1.5.5 shop in public_html, with dBase "zenc4"

In a subfolder, I have a development shop 2.2.1 with dBase "june26"

The subfolder dBase has already been upgraded with an earlier copy of the 1.5.5 dBase up to 2.2.1

There are no plug ins to consider.

The template for 2.2.2 is a modified responsive classic, emulating the existing 1.5.5 live shop appearance.

I now want to delete the 1.5.5 files. and copy all 2.2.1 files from the subfolder to the public_html.

I have taken (immediately before set in maintenance mode) a current copy of the 1.5.5 "zenc4" dBase, that I want to insert into the 2.2.1 shop once it sits in the public_html.

Is it ok to take the (1.5.5)"zenc4" dbase backup file, and import it into the (2.2.1)"june26" dBase?

and edit the 2.2.1 config files to remove the subfolder element in the address?

Any help appreciated.

Close, but one step is missing. The zenc4 backup is a 1.5.5 database: it has the 1.5.5 table structure. Import it as-is, and the 2.2.1 code will be running against a 1.5.5 database, which will break. It needs the same upgrade you already ran on june26.

Here's the order I'd use:

1. Import the fresh zenc4 backup into a new, empty database rather than overwriting june26. That way, june26 stays as a fallback if anything goes wrong.
2. Move the 2.2.1 files into public_html. Keep the old 1.5.5 files in a backup folder (outside public_html) instead of deleting them, at least until the new store is proven.
3. Copy the live images/ folder over the new one. Any product images added to the live store since you made the dev copy are only in the 1.5.5 tree.
4. Edit both configure files (includes/configure.php and your_admin/includes/configure.php):
   • DIR_WS_CATALOG and DIR_WS_HTTPS_CATALOG become '/'
   • DIR_FS_CATALOG becomes the full path to public_html (with a trailing slash)
   • DB_DATABASE (and user/password if different) point to the new database
   • Check that DB_CHARSET matches what the imported data actually is
5. Run zc_install in the new location and choose Database Upgrade. It will detect 1.5.5 and step the database up to 2.2.1.
6. Delete the zc_install folder when done.

One more thing: everything you set in the dev store's admin (template selection, layout boxes, configuration values, EZ-Pages, banners) lives in the database, so the import replaces it with the live 1.5.5 settings. Make a note of those dev changes before you start so you can reapply them. Define pages and the template files themselves are files, so they come across with the move.

Since you're doing the move anyway, it's worth going straight to 2.2.2 rather than 2.2.1. It's a small step and picks up the latest fixes.