{"id":51378,"date":"2026-03-31T06:48:25","date_gmt":"2026-03-31T06:48:25","guid":{"rendered":"https:\/\/crocoblock.com\/knowledge-base\/?post_type=article&p=51378"},"modified":"2026-03-31T09:22:52","modified_gmt":"2026-03-31T09:22:52","slug":"jetplugins-staging-to-live-checklist","status":"publish","type":"article","link":"https:\/\/crocoblock.com\/knowledge-base\/articles\/jetplugins-staging-to-live-checklist\/","title":{"rendered":"JetPlugins Staging to Live: Checklist"},"content":{"rendered":"\n

When migrating a site from staging to live or between the domains, the standard WordPress migration plugin moves files and database \u2014 but it does not move the Crocoblock license, does not update plugins applied to the domain, and does not guarantee saving JetEngine<\/em><\/a> structures, filters, and forms. This checklist will lead you step-by-step to ensure that all the data is migrated correctly. <\/p>\n\n\n\n

Migration Preparation<\/h2>\n\n\n\n
\n
    \n
  1. Back up your staging site. <\/li>\n<\/ol>\n\n\n\n

    It can be done using third-party plugins, through your hosting panel, or manually via FTP and phpMyAdmin. You can refer to the How to Backup and Restore WordPress Website with Plugin<\/strong><\/a> guide.<\/p>\n\n\n\n

      \n
    1. Note the list of active license keys. <\/li>\n<\/ol>\n\n\n\n

      Proceed to your Crocoblock account > My Licenses<\/em><\/strong> and note down or make a screenshot of the license keys active on the staging domain.<\/p>\n\n\n\n

      \"purchased<\/a><\/div>\n\n\n\n

      It is essential that you know for sure what licenses and how many of them are active on which domains beforehand. <\/p>\n\n\n\n

      3. Deactivate the Crocoblock license key on the staging site. <\/p>\n\n\n\n

      It can be done while proceeding to WordPress Admin > Crocoblock > License <\/em><\/strong>and clicking the \u201cDeactivate License<\/strong>\u201d button.<\/p>\n\n\n\n

      \"deactivate<\/a><\/div>\n\n\n\n

      Otherwise, open your Crocoblock account and click the\u201cManage Sites<\/strong>\u201d button next to the needed license. In the newly opened pop-up, click the \u201cDeactivate Site<\/strong>\u201d next to the needed staging domain. <\/p>\n\n\n\n

      \"deactivate<\/a><\/div>\n\n\n\n

      If the license is not deactivated on the staging site, the live site will be counted as a new activation that can exceed the activation limit. <\/p>\n\n\n\n

      4. Check the activation limit of your subscription plan<\/a>. <\/p>\n\n\n\n

      If you have a single-site plan<\/strong>, it means that the license key can be active on one site only at once. So staging and live sites cannot have the license key active simultaneously. You have to deactivate the license on the staging site before migration.<\/p>\n\n\n\n

      If you have an unlimited-sites plan<\/strong>, it is not necessary to deactivate the license from the staging site before migration. However, it is still recommended to remove the license key from the staging site once the site is migrated.<\/p>\n<\/div><\/div>\n\n\n\n

      JetEngine Structures Export<\/h2>\n\n\n\n
      \n
        \n
      1. Export all the JetEngine <\/em>structures through the Skins Manager<\/strong>. <\/li>\n<\/ol>\n\n\n\n

        Proceed to WordPress Dashboard > JetEngine > Skins Manager > Export<\/em><\/strong>. <\/p>\n\n\n\n

        Follow our How to Export and Import Custom Post Types, Terms and Meta Fields<\/strong><\/a> guide to ensure that the Custom Post Types<\/strong><\/a>, Custom Taxonomies<\/strong><\/a>, Meta Boxes<\/strong><\/a>, Relations<\/strong><\/a>, Options Pages<\/strong><\/a>, Query Builder<\/strong><\/a> queries, Listing Items<\/strong><\/a> (templates), and Custom Content Type<\/strong><\/a> structures are migrated.<\/p>\n\n\n\n

        \"export<\/a><\/div>\n\n\n\n

        Note that the Skins Manager<\/strong> moves the structure (how the CPT <\/strong>is set), but does not move the posts themselves. <\/p>\n\n\n\n

        2. Export CCT <\/strong>items separately.<\/p>\n\n\n\n

        Proceed to the needed Custom Content Type<\/strong>, select the needed items, and click the \u201dExport to CSV<\/strong>\u201d button. Refer to the How to Import and Export Custom Content Type<\/strong><\/a> guide for a detailed explanation.<\/p>\n\n\n\n

        \"export<\/a><\/div>\n\n\n\n

        Be aware that the WP All Export<\/em> plugin does not recognize CCT <\/strong>items because they are not WordPress posts. That\u2019s why standard export plugins do not work for the CCT <\/strong>data.<\/p>\n\n\n\n

        3. If you have custom fields in the CPT <\/strong>and need to export posts\u2019 data, use the WP All Export<\/em> plugin with the WP All Import<\/em> JetEngine Export<\/em><\/a> add-on.<\/p>\n\n\n\n

        Follow the How to Export and Import Custom Fields Using WP All Import<\/strong><\/a> guide to know how to migrate custom fields correctly.<\/p>\n<\/div><\/div>\n\n\n\n

        JetSmartFiters Export<\/h2>\n\n\n\n
        \n
          \n
        1. Export filters\u2019 settings.<\/li>\n<\/ol>\n\n\n\n

          You can export the filters\u2019 settings through the default WordPress Tools <\/strong>tab. Open the Export <\/strong>section and choose the \u201cSmart Filters\u201d option. Click the \u201cDownload Export File<\/strong>\u201d button.<\/p>\n\n\n\n

          \"export<\/a><\/div>\n\n\n
          <\/svg><\/div>
          Things to know<\/div>

          After the import, ensure that on the editing pages, the filters have the same Query IDs<\/strong><\/a> as the attached providers do. IDs might differ if the posts were imported, which can prevent filters from working correctly.<\/p><\/div><\/div>\n\n\n\n

          2. Filters with Dynamic Values.<\/p>\n\n\n\n

          In case filters use dynamic values from the meta fields<\/a>, ensure that the CPT <\/strong>and meta fields are already imported before you import the filters. <\/p>\n<\/div><\/div>\n\n\n\n

          JetFormBuilder\u2019s Forms Export<\/h2>\n\n\n\n
          \n
            \n
          1. Export every form.<\/li>\n<\/ol>\n\n\n\n

            Move to WordPress Dashboard > JetFormBuilder > All Forms<\/em><\/strong> and click the \u201cExport<\/strong>\u201d button next to the needed form. <\/p>\n\n\n\n

            \"export<\/a><\/div>\n\n\n\n

            The form will be saved in the JSON format with its structure, fields, conditions<\/a>, and actions<\/a>.<\/p>\n\n\n\n

            In case you have a form with Post Submit Action<\/strong><\/a>, Webhook<\/strong><\/a>, or Send Email<\/strong><\/a> action, after importing, check and ensure that all the actions are set up correctly. Pay attention to the email address and webhook URLs settings. <\/p>\n\n\n\n

            2. If the form is connected to the CPT <\/strong>or CCT<\/strong>.<\/p>\n\n\n\n

            First, import the JetEngine <\/em>structure (CPT<\/strong> or CCT <\/strong>with its data). Only then, import the form. Otherwise, form settings might be lost.<\/p>\n<\/div><\/div>\n\n\n\n

            Site Migration<\/h2>\n\n\n\n
            \n
              \n
            1. Move the files to the database.<\/li>\n<\/ol>\n\n\n\n

              Use the Duplicator<\/em>, All-in-One WP Migration<\/em>, or Migrate Guru<\/em> plugin. You can follow the How to Migrate a WordPress Website<\/strong><\/a> guide to ensure you are not missing any steps.  <\/p>\n\n\n\n

                \n
              1. Update URL in the database.<\/li>\n<\/ol>\n\n\n\n

                You can use WP-CLI to update URLs directly in the database of WordPress. It replaces every occurrence of the old domain with the new domain in all database tables. Here is an example command:<\/p>\n\n\n\n

                wp search-replace 'https:\/\/staging.example.com' 'https:\/\/example.com'<\/code><\/pre>\n\n\n\n
                Mind the following points:<\/p>\n\n\n\n