Created a new site on Local, imported an existing site SQL via AdminNeo, view Local site not shown correctly

Support
1

What issue or error are you experiencing?

I created a new site on Local, imported an existing site SQL via AdminNeo, and the Local site is not shown correctly as the imported site. There are different table format that was imported, I had copied the physical files in the Local Sites > “newsiteonlocal” example
Do I remove the Local table in AdminNeo for the other table to show up the data/site correctly?

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

Reviewing AdminNeo data
shows “customnamewp_test_wp…” and Local’s table “wp_…”
Do I remove the “wp_…”?? and other will take its place?

System Details

  • Local Version: The latest copy installed

  • Operating System (OS) and OS version:
    Windows 11

2

Hi @jniles-uw!

Yes, that’s the right approach, but your imported site has a custom table prefix (customnamewp_test_wp_) instead of the default prefix (wp_). WordPress needs to know which prefix to use which it reads this from wp-config.php.

You should be able to fix this in your Local site folder, open wp-config.php and find this line:

$table_prefix = 'wp_';

Change it to match your imported tables:

$table_prefix = 'customnamewp_test_wp_';

Save the file. This tells WordPress to look at the right tables.

Once your site loads correctly with the imported data, then you can safely delete the old wp_ tables in AdminNeo.

To delete in AdminNeo: select each wp_ table → click Drop (or check all and drop together).

Also you might need to check your Siteurl / Home URL as your imported database likely has the old site’s URL stored in customnamewp_test_wp_options. In AdminNeo:

  1. Open that _options table
  2. Find siteurl and home rows
  3. Update both values to your Local site URL (e.g. http://newsiteonlocal.local)

If you can’t log in after the switch, check that customnamewp_test_wp_usermeta has the right user capabilities row (wp_capabilities meta key may need updating to match the new prefix).