{"id":13222,"date":"2026-08-30T19:53:44","date_gmt":"2026-08-30T17:53:44","guid":{"rendered":"https:\/\/mybox.com\/help\/?post_type=manual_kb&#038;p=13222"},"modified":"2026-08-30T19:53:48","modified_gmt":"2026-08-30T17:53:48","slug":"cum-se-muta-un-site-web-bazat-pe-un-sistem-de-gestionare-a-continutului-cms-pe-o-platforma-de-gazduire-noua","status":"publish","type":"manual_kb","link":"https:\/\/mybox.com\/help\/ro\/knowledgebase\/how-to-move-a-concrete-cms-website-to-a-new-hosting-provider\/","title":{"rendered":"Cum s\u0103 muta\u021bi un site web CMS realizat \u00een Concrete la un nou furnizor de g\u0103zduire"},"content":{"rendered":"<div class=\"translation-block translation-block-merged\">\n<p class=\"wp-block-paragraph\">Moving a Concrete CMS website to a new hosting provider requires a complete copy of the site and a controlled DNS change. The safe sequence is to back up the current site, prepare the new hosting environment, transfer the database and files, update the configuration, test the new copy, and switch the domain only when the new site is ready.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/how-to-move-a-concrete-cms-website-to-a-new-hosting-provider\/#What_must_be_transferred\" >What must be transferred<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/how-to-move-a-concrete-cms-website-to-a-new-hosting-provider\/#1_Record_the_current_site_before_making_changes\" >1. Record the current site before making changes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/how-to-move-a-concrete-cms-website-to-a-new-hosting-provider\/#2_Create_and_check_backups\" >2. Create and check backups<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/how-to-move-a-concrete-cms-website-to-a-new-hosting-provider\/#3_Prepare_the_new_hosting_environment\" >3. Prepare the new hosting environment<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/how-to-move-a-concrete-cms-website-to-a-new-hosting-provider\/#4_Transfer_the_database_and_files\" >4. Transfer the database and files<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/how-to-move-a-concrete-cms-website-to-a-new-hosting-provider\/#5_Update_configuration_and_validate_PHP\" >5. Update configuration and validate PHP<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/how-to-move-a-concrete-cms-website-to-a-new-hosting-provider\/#6_Rebuild_the_cache_and_test_the_copied_site\" >6. Rebuild the cache and test the copied site<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/how-to-move-a-concrete-cms-website-to-a-new-hosting-provider\/#7_Change_DNS_after_testing\" >7. Change DNS after testing<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/how-to-move-a-concrete-cms-website-to-a-new-hosting-provider\/#8_Verify_the_live_site_and_keep_a_rollback_path\" >8. Verify the live site and keep a rollback path<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/how-to-move-a-concrete-cms-website-to-a-new-hosting-provider\/#When_the_migration_is_complete\" >When the migration is complete<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_must_be_transferred\"><\/span>What must be transferred<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A Concrete CMS migration is more than copying visible page content. The transfer should include the website database and all files that belong to the installation. Together, these preserve the site structure and its working data.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Concrete CMS pages and page structure<\/li>\n\n\n\n<li>Uploaded files and media<\/li>\n\n\n\n<li>User accounts and permissions<\/li>\n\n\n\n<li>Forms and their stored configuration or data<\/li>\n\n\n\n<li>Site settings and the current Concrete CMS configuration<\/li>\n\n\n\n<li>Search-related page content and URL structure<\/li>\n<\/ul>\n\n\n\n<\/div>\n\n<div id=\"mybox-182826214\" class=\"mybox-content mybox-entity-placement\"><div class=\"early-access-banner-inpost\">\r\n  <div class=\"banner-left-inpost\">\r\n    <div class=\"icon-box-inpost\">\r\n      <img decoding=\"async\" src=\"https:\/\/mybox.com\/help\/wp-content\/uploads\/2026\/02\/square-info-icon.svg\" alt=\"Info\">\r\n    <\/div>\r\n    <div class=\"text-box-inpost\">\r\n      <span class=\"label-inpost\"><span class=\"translation-block translation-block-banner-text\">Acces timpuriu<\/span><\/span>\r\n      <h4><span class=\"translation-block translation-block-banner-text\">Mai ave\u021bi nevoie de ajutor?<\/span><\/h4>\r\n      <p><span class=\"translation-block translation-block-banner-text\">Contacta\u021bi echipa noastr\u0103 de servicii pentru clien\u021bi.<\/span><\/p>\r\n    <\/div>\r\n  <\/div>\r\n\r\n  <div class=\"banner-right-inpost\">\r\n    <a href=\"https:\/\/panel.mybox.com\/helpdesk2\/v\/list\/\" class=\"banner-button-inpost\"><span class=\"translation-block translation-block-banner-text\">Trimite mesaj<\/span><\/a>\r\n  <\/div>\r\n<\/div><\/div>\n\n<div class=\"translation-block translation-block-merged\"><p class=\"wp-block-paragraph\">Keep the current hosting environment active while the new copy is prepared and tested. A staged migration keeps the existing website available until the new environment is ready. <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/cum-se-muta-un-site-web-typo3-la-un-nou-furnizor-de-gazduire-fara-intreruperi-de-functionare\/\">The same staged approach is recommended for a website migration without downtime<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"1_Record_the_current_site_before_making_changes\"><\/span>1. Record the current site before making changes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Start by recording the current Concrete CMS version, the PHP version used by the site, the database details, the domain, and any custom configuration. This information gives you a reference when preparing the new hosting environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check version compatibility before transferring the site. The Concrete CMS version and the PHP version on the new server must be suitable for the website. Confirm this before the final DNS change so that compatibility problems can be handled while the old site is still available.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"2_Create_and_check_backups\"><\/span>2. Create and check backups<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Create a full backup of the Concrete CMS database and the complete website files. Keep the backup separate from the current hosting account where possible. The database contains the site&#8217;s structured content and settings, while the files include the application and uploaded resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Make sure the backup can be accessed before continuing. Also keep the current website unchanged during the transfer. The old environment is the rollback point if the new server does not pass testing.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"3_Prepare_the_new_hosting_environment\"><\/span>3. Prepare the new hosting environment<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Set up the new hosting space without changing the live domain yet. Match the recorded PHP requirements and prepare a database for the Concrete CMS site. The new environment should be ready to receive both the database backup and the website files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not point the domain to the new server at this stage. The domain should be switched only after the transferred copy has been configured and tested. This separation lets you correct configuration or compatibility issues without taking the current site offline.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"4_Transfer_the_database_and_files\"><\/span>4. Transfer the database and files<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Move the complete website files to the new hosting environment.<\/li>\n\n\n\n<li>Import the database backup into the new database.<\/li>\n\n\n\n<li>Keep the directory structure required by the Concrete CMS installation.<\/li>\n\n\n\n<li>Check that the transferred files and imported database belong to the same backup point.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Using matching copies is important because the database and files work together. A database from one point in time combined with files from another point can produce an incomplete or inconsistent site.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"5_Update_configuration_and_validate_PHP\"><\/span>5. Update configuration and validate PHP<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Update the Concrete CMS configuration on the new server with the new database connection details and the settings required by the new hosting environment. Review the site URL and any hosting-specific paths or values that changed during the move.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Validate the PHP version before opening the site to visitors. Then load the site through the new environment and check that Concrete CMS starts without errors. If the application does not load, keep the old site active while you review the configuration and PHP compatibility.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"6_Rebuild_the_cache_and_test_the_copied_site\"><\/span>6. Rebuild the cache and test the copied site<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Rebuild or clear the Concrete CMS cache after the files, database, and configuration are in place. This ensures that the new environment is tested with refreshed cached data rather than relying on values created on the old server.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Test the copied site before changing DNS. Use a complete test pass that includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Important pages and navigation<\/li>\n\n\n\n<li>Uploaded files, images, and downloads<\/li>\n\n\n\n<li>Concrete CMS user sign-in<\/li>\n\n\n\n<li>User permissions and restricted areas<\/li>\n\n\n\n<li>Forms and their submission flow<\/li>\n\n\n\n<li>Search functions and page visibility<\/li>\n\n\n\n<li>Page URLs, redirects, and internal links<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Moving a website to a new server does not normally harm search engine ranking when the site remains available and its important URLs and content are preserved. <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/mutarea-unui-site-web-pe-un-nou-server-va-afecta-clasamentul-acestuia-in-motoarele-de-cautare\/\">Search visibility depends on carrying out the move without disrupting the website structure and access<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"7_Change_DNS_after_testing\"><\/span>7. Change DNS after testing<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When the new Concrete CMS copy passes testing, update the domain&#8217;s DNS settings so the domain points to the new hosting environment. Leave the old hosting active while the DNS change spreads.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">DNS propagation typically takes a few hours, but it can take longer depending on the domain registrar and network conditions. During this period, some visitors may still reach the old server while others reach the new one. <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/cum-sa-va-pregatiti-pentru-migrarea-unui-site-web-catre-un-nou-server\/\">Planning the transfer and allowing time for DNS changes are part of preparing a website migration<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"8_Verify_the_live_site_and_keep_a_rollback_path\"><\/span>8. Verify the live site and keep a rollback path<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After the DNS change, test the live domain again. Check pages, files, users, permissions, forms, search, and the Concrete CMS cache. Also confirm that the site is still using the intended PHP version and that the main URLs open correctly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the new server fails, do not remove the old hosting environment. Restore the domain&#8217;s DNS settings to the previous hosting destination, then allow DNS propagation to complete. Keep the new copy available for diagnosis, correct the configuration or compatibility issue, rebuild the cache, and test again before repeating the DNS switch.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"When_the_migration_is_complete\"><\/span>When the migration is complete<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The migration is complete when the new server serves the expected Concrete CMS content and functions, the domain resolves to the new environment, and the post-migration checks pass. Keep the backup and the old hosting environment until the new site has been stable for a suitable operational period.<\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"template":"","format":"standard","manualknowledgebasecat":[36],"manual_kb_tag":[],"class_list":["post-13222","manual_kb","type-manual_kb","status-publish","format-standard","hentry","manualknowledgebasecat-migration"],"_links":{"self":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/13222","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/13222\/revisions"}],"predecessor-version":[{"id":13238,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/13222\/revisions\/13238"}],"wp:attachment":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/media?parent=13222"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manualknowledgebasecat?post=13222"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb_tag?post=13222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}