Support » Plugin: All-in-One WP Migration » How to copy WP Standalone Site into a WP Multisite Network with AIO WP Migration

  • Resolved frank tredici

    (@frank13)


    I am running a WordPress multisite network on the latest version of WP 4.6.1

    I need to migrate a standalone s2Member WordPress site running version 4.5.4

    The standalone WP site contains:

    • 591 Posts
    • 9 post Categories
    • 526 post Tags
    • 327 media library files
    • 35 Pages
    • 1,067 Comments
    • 1 Theme
    • 23 Plugins (including s2Member)
    • 1,259 Users (128 users are paid-for s2Member subscribers through recurring PayPal subscription renewals)

    Does or can your All-in-One WP Migration plugin handle a migration of this nature (a) keeping all content in tact and (b) all user accounts and subscriptions in tact?

    Any advice or suggestions you may have is greatly appreciated. Thank you.

    • This topic was modified 2 years, 6 months ago by  frank tredici.
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Borislav Angelov

    (@bangelov)

    Hi

    Yes, you shouldn’t have any problem with the described migration. Basically the only thing that you may need is to re-configure s2member plugin because probably it has own license mechanism depending on the type of the purchased license that you need to use the plugin.

    Do not hesitate to contact us if you face any issue.

    So out of curiosity, how do I map the migration?

    The SOURCE standalone DB table names are wp_* while the TARGET multisite database table names are wp_22_*

    In certain instances, the source wp_* tables will conflict with the target multistage core tables at wp_* …

    • This reply was modified 2 years, 5 months ago by  frank tredici.
    • This reply was modified 2 years, 5 months ago by  frank tredici.
    Plugin Author Borislav Angelov

    (@bangelov)

    Hi

    Table prefixes will be replaced automatically on import. For instance if your SOURCE standalone site has wp_* table prefix and your TARGET multisite has wp_22_*, all tables from source site will be mapped to the TARGET table prefix like that wp_22_N_* where N is the ID of the subsite. ID is automatically generated when new subsite is created. You can also overwrite existing subsite if you specify the same URL as the existing one on import screen.

    But how does your plugin know the target table ID=22? (i.e., wp_22_*)

    Do I manually provide the ID of the subsite at time of import?

    Or does your plugin automatically grab the next ID from the auto incr value? If so, then I would need to manually rename the tables after import to move them from wp_(AI+1)_* to wp_22_* — correct?

    • This reply was modified 2 years, 5 months ago by  frank tredici.
    • This reply was modified 2 years, 5 months ago by  frank tredici.
    • This reply was modified 2 years, 5 months ago by  frank tredici.
    • This reply was modified 2 years, 5 months ago by  frank tredici.
    • This reply was modified 2 years, 5 months ago by  frank tredici.
    Plugin Author Borislav Angelov

    (@bangelov)

    Hi

    On the import screen, you will be asked to enter subsite URL. If given subsite URL exists in the database (we check that by using WP function called domain_exists()), we get existing subsite ID and use it in the process of generating table prefixes. For instance if subsite URL http://subsite.example.org exists in your TARGET multisite and it has ID = 4 but your network has table prefix wp_22_*, subsite tables will be under wp_22_4_*.

    If given subsite URL does not exist, plugin will automatically create new subsite and the new subsite ID will be used to prefix all tables like if the new ID = 5, tables for that subsite will be under wp_22_5_*

    Ok. Hope it works. You are missing the naming convention of my tables.

    My tables are wp_ID_* … not wp_22_ID_*

    “22” in my post is the ID.

    I’ll post back on the results.

    Plugin Author Borislav Angelov

    (@bangelov)

    Hi

    Sorry I thought your WordPress has wp_22_ as global table prefix however both ways it will work.

    Keep me posted if you face any issue.

    Question. It costs $179 to migrate from standalone to multisite?

    Plugin Author Borislav Angelov

    (@bangelov)

    Hi

    There are many scenarios supported by the plugin.

    Export single site from the network
    Export multiple sites from the network
    Export the whole network
    Import single site into the network
    Import multiple sites into the network
    Import a network
    Clone single site within a network
    Multi-network support

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘How to copy WP Standalone Site into a WP Multisite Network with AIO WP Migration’ is closed to new replies.