{"id":2838,"date":"2026-05-14T07:30:00","date_gmt":"2026-05-14T07:30:00","guid":{"rendered":"https:\/\/www.serverspan.com\/blog\/"},"modified":"2026-05-14T07:30:01","modified_gmt":"2026-05-14T07:30:01","slug":"ghid-migrare-cpanel-directadmin-2026-muta-conturi-baze-de-date-email-dns-ssl-si-backupuri-in-siguranta-cu-rollback-testat-pas-cu-pas","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/ghid-migrare-cpanel-directadmin-2026-muta-conturi-baze-de-date-email-dns-ssl-si-backupuri-in-siguranta-cu-rollback-testat-pas-cu-pas\/","title":{"rendered":"Ghid migrare cPanel DirectAdmin 2026: mut\u0103 conturi, baze de date, email, DNS, SSL \u0219i backupuri \u00een siguran\u021b\u0103, cu rollback testat pas cu pas."},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">O migrare cPanel DirectAdmin \u00eencepe cu un backup complet al contului cPanel, un server DirectAdmin curat, transfer controlat, conversie cu unealta oficial\u0103 DirectAdmin pentru backupuri cPanel \u0219i verificarea site-urilor, bazelor de date, emailului, DNS-ului, SSL-ului, cron joburilor \u0219i c\u0103ilor din aplica\u021bii. Procesul sigur nu este \u201ecopiem fi\u0219ierele \u0219i sper\u0103m\u201d. Procesul sigur este o migrare etapizat\u0103, cu punct de rollback, fereastr\u0103 scurt\u0103 de cutover DNS \u0219i f\u0103r\u0103 anularea contului vechi cPanel p\u00e2n\u0103 c\u00e2nd toate serviciile au fost testate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Motivul pentru care conteaz\u0103 \u00een 2026 este simplu. Multe companii de hosting, agen\u021bii \u0219i proprietari de servere s-au s\u0103turat de costurile tot mai mari ale licen\u021belor cPanel \u0219i caut\u0103 o alternativ\u0103 practic\u0103. DirectAdmin este de obicei cea mai curat\u0103 destina\u021bie, pentru c\u0103 suport\u0103 hosting multi-user, structuri reseller, domenii, baze de date, mailboxuri, DNS, SSL, backupuri \u0219i un flux familiar de control panel, f\u0103r\u0103 s\u0103 for\u021beze clien\u021bii \u00eentr-un model de operare complet diferit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ghidul acesta este scris pentru sysadmini, agen\u021bii, reselleri de hosting \u0219i furnizori mici care trebuie s\u0103 migreze conturi reale f\u0103r\u0103 pierdere de date. Dac\u0103 vrei ca migrarea s\u0103 fie f\u0103cut\u0103 pentru tine, <a href=\"https:\/\/www.serverspan.ro\/directadmin-management\">administrarea DirectAdmin ServerSpan<\/a> este punctul firesc de handoff. Dac\u0103 o faci singur, urmeaz\u0103 runbook-ul \u00een ordine.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u00cenainte de migrare: ce presupune acest ghid<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ghidul presupune c\u0103 ai:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>acces root la serverul surs\u0103 cPanel<\/li>\n\n\n\n<li>acces root la serverul destina\u021bie DirectAdmin<\/li>\n\n\n\n<li>spa\u021biu liber suficient pe ambele servere pentru backupuri complete de cont<\/li>\n\n\n\n<li>SSH func\u021bional \u00eentre cele dou\u0103 servere<\/li>\n\n\n\n<li>o instalare DirectAdmin recent\u0103 pe un sistem de operare suportat<\/li>\n\n\n\n<li>timp pentru propagare DNS \u0219i testare post-migrare<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 ai doar login de utilizator cPanel \u0219i nu ai acces root, po\u021bi migra \u00een continuare, dar procesul se schimb\u0103. Vei avea nevoie de backupuri complete de cont din interfa\u021ba cPanel sau de ajutorul furnizorului. Nu vei putea rula singur <code>\/scripts\/pkgacct<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Nu \u00eencepe o migrare de produc\u021bie de pe un server nepatchuit sau c\u0103tre un nod DirectAdmin construit pe jum\u0103tate. Rezolv\u0103 \u00eent\u00e2i sistemul de operare, hostname-ul, resolverul, firewallul, licen\u021ba DirectAdmin, nameserverele, calea de backup \u0219i stackul de mail. O migrare este suficient de complicat\u0103 f\u0103r\u0103 s\u0103 depanezi \u00een acela\u0219i timp o destina\u021bie stricat\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Checklist \u00eenainte de migrare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ruleaz\u0103 acest checklist \u00eenainte s\u0103 atingi datele conturilor:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Scade TTL-ul DNS la 300 de secunde cu cel pu\u021bin 24 de ore \u00eenainte de migrare.<\/li>\n\n\n\n<li>Noteaz\u0103 nameserverele curente, \u00eenregistr\u0103rile A, MX, TXT, SPF, DKIM \u0219i DMARC.<\/li>\n\n\n\n<li>Export\u0103 sau salveaz\u0103 screenshoturi cu zonele DNS custom \u00eenainte s\u0103 modifici ceva.<\/li>\n\n\n\n<li>Listeaz\u0103 toate conturile cPanel, domeniile, addon domains, parked domains \u0219i subdomeniile.<\/li>\n\n\n\n<li>Listeaz\u0103 toate bazele de date \u0219i utilizatorii de baze de date.<\/li>\n\n\n\n<li>Listeaz\u0103 toate mailboxurile, forwarderele, autoresponderele, filtrele \u0219i mailing listurile.<\/li>\n\n\n\n<li>Verific\u0103 disk usage pe serverul surs\u0103 \u0219i pe serverul destina\u021bie.<\/li>\n\n\n\n<li>Verific\u0103 versiunile PHP folosite de site-uri.<\/li>\n\n\n\n<li>Verific\u0103 cron joburile \u0219i c\u0103ile hardcodate.<\/li>\n\n\n\n<li>F\u0103 un backup independent, off-server, \u00eenainte s\u0103 \u00eencepi.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Pasul cu TTL-ul DNS nu este cosmetic. Dac\u0103 TTL-ul curent este 14400 de secunde sau mai mare \u0219i schimbi nameserverele f\u0103r\u0103 preg\u0103tire, unii vizitatori \u0219i unele servere de mail pot continua s\u0103 loveasc\u0103 serverul vechi ore \u00eentregi. Sc\u0103derea TTL-ului \u00eenainte de migrare \u00ee\u021bi ofer\u0103 un cutover mai curat \u0219i un rollback mai rapid dac\u0103 ceva se rupe.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Procesul de migrare cPanel la DirectAdmin \u00een 10 pa\u0219i<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 1: genereaz\u0103 un backup complet al contului cPanel<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Pe serverul cPanel, genereaz\u0103 un backup complet pentru fiecare cont. Cu acces root, comanda standard este:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/scripts\/pkgacct USERNAME \/home<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Asta creeaz\u0103 un fi\u0219ier de backup de forma:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/home\/cpmove-USERNAME.tar.gz<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru mai multe conturi, creeaz\u0103 \u00eent\u00e2i o list\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ls \/var\/cpanel\/users &gt; \/root\/cpanel-users.txt<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apoi \u00eempacheteaz\u0103 conturile pe r\u00e2nd. Nu rula orbe\u0219te un loop masiv pe un server de produc\u021bie ocupat f\u0103r\u0103 s\u0103 verifici spa\u021biul liber. Backupurile complete de cont pot consuma mult I\/O \u0219i mult storage, mai ales pe servere cu mailboxuri mari.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>df -h\ndu -sh \/home\/* | sort -h<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 serverul surs\u0103 are spa\u021biu redus, mut\u0103 backupurile vechi \u00een afara ma\u0219inii sau genereaz\u0103 pachetele c\u0103tre o cale de storage montat\u0103 separat.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 2: transfer\u0103 backupul cPanel pe serverul DirectAdmin<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Creeaz\u0103 un director curat de import pe serverul DirectAdmin:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mkdir -p \/home\/admin\/cpanel_backups<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">De pe serverul cPanel, transfer\u0103 pachetul cu <code>rsync<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>rsync -avz --progress \/home\/cpmove-USERNAME.tar.gz root@DIRECTADMIN_IP:\/home\/admin\/cpanel_backups\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru conturi mari, <code>rsync<\/code> este mai sigur dec\u00e2t o desc\u0103rcare prin browser, pentru c\u0103 gestioneaz\u0103 mai bine transferurile \u00eentrerupte \u0219i afi\u0219eaz\u0103 progresul. Dup\u0103 transfer, verific\u0103 dimensiunea fi\u0219ierului pe ambele servere:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ls -lh \/home\/cpmove-USERNAME.tar.gz\nssh root@DIRECTADMIN_IP 'ls -lh \/home\/admin\/cpanel_backups\/cpmove-USERNAME.tar.gz'<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru mailboxuri foarte mari, f\u0103 transferul \u00eentr-o perioad\u0103 lini\u0219tit\u0103. Structurile Maildir cu sute de mii de fi\u0219iere mici pot dura mai mult dec\u00e2t sugereaz\u0103 dimensiunea brut\u0103 a datelor.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 3: converte\u0219te backupul cPanel cu unealta DirectAdmin de migrare<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">DirectAdmin ofer\u0103 o unealt\u0103 oficial\u0103 de conversie cPanel c\u0103tre DirectAdmin. C\u0103ile pot varia \u00eentre versiunile DirectAdmin, deci verific\u0103 documenta\u021bia oficial\u0103 de migrare DirectAdmin \u00eenainte s\u0103 rulezi procesul pe produc\u021bie. Fluxul comun folose\u0219te scriptul de conversie din directorul shared de migrare al DirectAdmin:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/usr\/local\/directadmin\/shared\/cpanel_to_da\n.\/cpanel_to_da.sh \/home\/admin\/cpanel_backups\/cpmove-USERNAME.tar.gz<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pe unele instal\u0103ri, unealta a\u0219teapt\u0103 backupurile \u00eentr-un anumit director \u0219i scrie fi\u0219ierele convertite de backup DirectAdmin \u00eentr-o cale de output. Nu ghici. Cite\u0219te help-ul scriptului sau documenta\u021bia oficial\u0103 de pe serverul destina\u021bie:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/usr\/local\/directadmin\/shared\/cpanel_to_da\n.\/cpanel_to_da.sh --help 2&gt;\/dev\/null || ls -lah<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 conversie, restaureaz\u0103 backupul DirectAdmin convertit prin interfa\u021ba DirectAdmin de admin backup restore sau prin metoda CLI recomandat\u0103 de documenta\u021bia DirectAdmin curent\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Punctul opera\u021bional important este acesta: conversia nu \u00eenseamn\u0103 verificare. Un log de conversie reu\u0219it\u0103 \u00eenseamn\u0103 doar c\u0103 unealta a terminat. Nu dovede\u0219te c\u0103 fiecare site, mailbox, baz\u0103 de date, cron job, \u00eenregistrare DNS \u0219i certificat SSL func\u021bioneaz\u0103.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 4: verific\u0103 bazele de date \u0219i configura\u021bia aplica\u021biilor<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 restore, verific\u0103 dac\u0103 bazele de date \u0219i utilizatorii de baze de date exist\u0103 \u00een DirectAdmin. Pentru site-uri WordPress, verific\u0103 <code>wp-config.php<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep -E \"DB_NAME|DB_USER|DB_HOST|table_prefix\" \/home\/USERNAME\/domains\/DOMAIN\/public_html\/wp-config.php<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Problemele comune includ:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>utilizatorul de baz\u0103 de date s-a schimbat \u00een timpul conversiei<\/li>\n\n\n\n<li>prefixul numelui bazei de date difer\u0103 fa\u021b\u0103 de cPanel<\/li>\n\n\n\n<li><code>DB_HOST<\/code> \u00eenc\u0103 pointeaz\u0103 spre un vechi host MySQL remote<\/li>\n\n\n\n<li>c\u0103i absolute hardcodate \u00eenc\u0103 refer\u0103 <code>\/home\/olduser\/public_html<\/code><\/li>\n\n\n\n<li>versiunea PHP difer\u0103 de cea folosit\u0103 \u00een contul vechi cPanel<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Testeaz\u0103 manual autentificarea la baza de date:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mysql -u DB_USER -p DB_NAME<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru WordPress, activeaz\u0103 debug logging doar \u00een timpul depan\u0103rii:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>define( 'WP_DEBUG', true );\ndefine( 'WP_DEBUG_LOG', true );\ndefine( 'WP_DEBUG_DISPLAY', false );<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apoi verific\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>tail -f \/home\/USERNAME\/domains\/DOMAIN\/public_html\/wp-content\/debug.log<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Opre\u0219te afi\u0219area erorilor dup\u0103 testare. Erorile vizibile pe un site de produc\u021bie sunt o neglijen\u021b\u0103 \u0219i pot expune c\u0103i sau detalii despre pluginuri.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 5: verific\u0103 \u0219i sincronizeaz\u0103 emailul cu aten\u021bie<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Migr\u0103rile de la cPanel la DirectAdmin pot restaura mailboxuri, dar emailul merit\u0103 aten\u021bie separat\u0103, pentru c\u0103 mesajele pot ajunge \u00een timpul ferestrei de migrare. Cea mai sigur\u0103 abordare este s\u0103 p\u0103strezi serviciul de mail cPanel online p\u00e2n\u0103 dup\u0103 cutoverul DNS \u0219i apoi s\u0103 rulezi o sincronizare IMAP final\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instaleaz\u0103 <code>imapsync<\/code> pe o ma\u0219in\u0103 temporar\u0103 de administrare sau pe un server de migrare:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt update\napt install imapsync<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apoi sincronizeaz\u0103 un mailbox de pe vechiul server pe cel nou:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>imapsync \\\n  --host1 old.mail.server \\\n  --user1 user@domain.com \\\n  --password1 'OLD_PASSWORD' \\\n  --host2 new.mail.server \\\n  --user2 user@domain.com \\\n  --password2 'NEW_PASSWORD' \\\n  --ssl1 --ssl2<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru multe mailboxuri, scriptarea dintr-un fi\u0219ier CSV este mai sigur\u0103 dec\u00e2t rularea manual\u0103 a comenzilor. Anun\u021b\u0103 \u0219i utilizatorii \u00eenainte de migrare. Dac\u0103 folosesc clien\u021bi de mail desktop, s-ar putea s\u0103 trebuiasc\u0103 s\u0103 actualizeze numele serverelor, porturile \u0219i parolele dup\u0103 cutover.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103 folderele de mail, mesajele trimise, statusul citit\/necitit, forwarderele, autoresponderele, set\u0103rile anti-spam \u0219i filtrele. Nu presupune c\u0103 emailul este \u00een regul\u0103 doar pentru c\u0103 inboxul exist\u0103.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 6: verific\u0103 zonele DNS \u00eenainte s\u0103 schimbi nameserverele<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte s\u0103 schimbi nameserverele, compar\u0103 \u00eenregistr\u0103rile DNS din cPanel \u0219i DirectAdmin. Aici se stric\u0103 multe migr\u0103ri de email sau servicii ter\u021be.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig DOMAIN A\ndig DOMAIN MX\ndig DOMAIN TXT\ndig www.DOMAIN CNAME\ndig _dmarc.DOMAIN TXT<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Tipuri de \u00eenregistr\u0103ri de verificat:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A \u0219i AAAA pentru domeniul principal \u0219i subdomenii<\/li>\n\n\n\n<li>CNAME pentru www \u0219i aliasuri de servicii<\/li>\n\n\n\n<li>MX pentru rutarea emailului<\/li>\n\n\n\n<li>TXT pentru SPF, DKIM, DMARC, Google, Microsoft, gateway-uri de plat\u0103 \u0219i servicii de verificare<\/li>\n\n\n\n<li>SRV dac\u0103 domeniul folose\u0219te servicii speciale de mail sau colaborare<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Nu suprascrie o zon\u0103 DNS doar cu \u00eenregistr\u0103rile pentru website. Multe domenii depind de TXT-uri ascunse pentru email, analytics, procesatori de plat\u0103, CRM-uri \u0219i servicii SaaS. Pierderea unei singure \u00eenregistr\u0103ri TXT poate rupe un proces de business pe care nimeni nu \u00eel asociaz\u0103 cu migrarea dec\u00e2t dup\u0103 c\u00e2teva zile.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 7: reemite certificatele SSL \u00een DirectAdmin<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Certificatele SSL din cPanel nu se mapeaz\u0103 \u00eentotdeauna curat \u00een DirectAdmin. \u00cen majoritatea cazurilor, calea curat\u0103 este emiterea unor certificate Let&#8217;s Encrypt noi dup\u0103 ce DNS-ul pointeaz\u0103 c\u0103tre serverul DirectAdmin.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte de cutover, po\u021bi testa site-ul local edit\u00e2nd fi\u0219ierul hosts de pe sta\u021bia ta \u0219i point\u00e2nd domeniul c\u0103tre IP-ul DirectAdmin. Dup\u0103 cutoverul DNS, emite sau reemite SSL din DirectAdmin.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103 HTTPS dup\u0103 emitere:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -I https:\/\/DOMAIN\nopenssl s_client -connect DOMAIN:443 -servername DOMAIN &lt;\/dev\/null 2&gt;\/dev\/null | openssl x509 -noout -subject -issuer -dates<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 emiterea certificatului e\u0219ueaz\u0103, verific\u0103 \u00eent\u00e2i DNS-ul. Validarea HTTP Let&#8217;s Encrypt va e\u0219ua dac\u0103 domeniul \u00eenc\u0103 pointeaz\u0103 c\u0103tre serverul vechi cPanel sau dac\u0103 firewallul blocheaz\u0103 portul 80.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 8: verific\u0103 SPF, DKIM \u0219i DMARC<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Autentificarea emailului se rupe adesea \u00een t\u0103cere \u00een timpul migr\u0103rilor de panel. Dac\u0103 DirectAdmin devine noul expeditor de email, SPF \u0219i DKIM trebuie s\u0103 reflecte asta. Dac\u0103 emailul r\u0103m\u00e2ne la un furnizor ter\u021b, nu \u00eenlocui acele \u00eenregistr\u0103ri cu valorile locale implicite.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig DOMAIN TXT\ndig default._domainkey.DOMAIN TXT\ndig _dmarc.DOMAIN TXT<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Probleme SPF tipice dup\u0103 migrare:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>IP-ul vechiului server cPanel r\u0103m\u00e2ne \u00een SPF, dar IP-ul DirectAdmin lipse\u0219te<\/li>\n\n\n\n<li>domeniul are dou\u0103 \u00eenregistr\u0103ri SPF conflictuale<\/li>\n\n\n\n<li>un expeditor ter\u021b a fost eliminat accidental<\/li>\n\n\n\n<li>domeniul trimite acum prin DirectAdmin, dar DKIM nu este activat<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Trimite un email real de test c\u0103tre Gmail, Outlook \u0219i un mailbox pe care \u00eel controlezi. Verific\u0103 headerele. Nu te baza doar pe mesajul \u201esent successfully\u201d din interfa\u021ba de webmail.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 9: testeaz\u0103 toate serviciile dup\u0103 cutover<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 schimbarea nameserverelor sau a \u00eenregistr\u0103rilor A, testeaz\u0103 site-ul ca utilizator \u0219i ca sysadmin.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103ri pentru website:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>pagina principal\u0103 se \u00eencarc\u0103 prin HTTPS<\/li>\n\n\n\n<li>loginul de admin func\u021bioneaz\u0103<\/li>\n\n\n\n<li>formularele se trimit corect<\/li>\n\n\n\n<li>uploadurile func\u021bioneaz\u0103<\/li>\n\n\n\n<li>pretty permalinks func\u021bioneaz\u0103<\/li>\n\n\n\n<li>cron joburile ruleaz\u0103<\/li>\n\n\n\n<li>versiunea PHP este corect\u0103<\/li>\n\n\n\n<li>logurile de eroare sunt curate<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103ri din linia de comand\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -I https:\/\/DOMAIN\ncurl -I https:\/\/www.DOMAIN\ndig @1.1.1.1 DOMAIN A +short\ndig @8.8.8.8 DOMAIN MX +short\ntail -n 100 \/var\/log\/httpd\/domains\/DOMAIN.error.log 2&gt;\/dev\/null\ntail -n 100 \/var\/log\/nginx\/domains\/DOMAIN.error.log 2&gt;\/dev\/null\ntail -n 100 \/var\/log\/exim\/mainlog 2&gt;\/dev\/null<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103ri pentru email:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>loginul webmail func\u021bioneaz\u0103<\/li>\n\n\n\n<li>IMAP func\u021bioneaz\u0103 dintr-un client desktop<\/li>\n\n\n\n<li>autentificarea SMTP func\u021bioneaz\u0103<\/li>\n\n\n\n<li>emailul inbound ajunge<\/li>\n\n\n\n<li>emailul outbound ajunge la Gmail \u0219i Outlook<\/li>\n\n\n\n<li>forwarderele \u0219i autoresponderele func\u021bioneaz\u0103<\/li>\n\n\n\n<li>filtrarea anti-spam se comport\u0103 cum trebuie<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru WordPress \u0219i WooCommerce, plaseaz\u0103 o comand\u0103 de test dac\u0103 este posibil. Un magazin care se \u00eencarc\u0103, dar nu poate trimite emailuri de comand\u0103 sau nu poate procesa checkoutul nu este migrat.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pasul 10: p\u0103streaz\u0103 contul vechi cPanel p\u00e2n\u0103 c\u00e2nd rollbackul nu mai este necesar<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Nu anula contul vechi cPanel \u00een ziua migr\u0103rii. P\u0103streaz\u0103-l online cel pu\u021bin 7 p\u00e2n\u0103 la 14 zile, mai mult pentru migr\u0103ri complexe de email sau magazine cu valoare ridicat\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte de anulare, confirm\u0103 c\u0103:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>to\u021bi resolverii DNS pointeaz\u0103 c\u0103tre noul server DirectAdmin<\/li>\n\n\n\n<li>traficul web recent nu mai ajunge pe vechiul server cPanel<\/li>\n\n\n\n<li>emailul nu mai ajunge pe vechiul server<\/li>\n\n\n\n<li>to\u021bi utilizatorii pot accesa mailul pe noul server<\/li>\n\n\n\n<li>toate bazele de date \u0219i aplica\u021biile sunt stabile<\/li>\n\n\n\n<li>exist\u0103 backupuri off-server pentru noul mediu DirectAdmin<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Pe serverul vechi, verific\u0103 logurile \u00eenainte s\u0103 opre\u0219ti ceva:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>tail -f \/usr\/local\/apache\/logs\/access_log\ntail -f \/var\/log\/exim_mainlog<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 serverul vechi \u00eenc\u0103 prime\u0219te trafic sau email relevant, nu \u00eel anula. Afl\u0103 de ce. Cache-uri DNS, MX-uri uitate, IP-uri hardcodate \u0219i integr\u0103ri externe pot \u021bine infrastructura veche \u00een via\u021b\u0103 mai mult dec\u00e2t te a\u0219tep\u021bi.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Plan de rollback: ce faci dac\u0103 migrarea e\u0219ueaz\u0103<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Un plan real de migrare include rollback. Dac\u0103 partea DirectAdmin se rupe grav, ai nevoie de o cale curat\u0103 \u00eenapoi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rollbackul cere trei lucruri:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>contul vechi cPanel \u00eenc\u0103 online<\/li>\n\n\n\n<li>TTL DNS sc\u0103zut \u00eenainte de migrare<\/li>\n\n\n\n<li>f\u0103r\u0103 scrieri ireversibile pierdute \u00een fereastra de cutover<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 rollbackul este necesar, pointeaz\u0103 DNS-ul \u00eenapoi c\u0103tre IP-ul sau nameserverele vechi cPanel:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig DOMAIN A +short\ndig DOMAIN NS +short<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apoi reverific\u0103 website-ul \u0219i mailul pe serverul vechi. Dac\u0103 site-ul a acceptat comenzi, formulare sau modific\u0103ri de utilizator pe serverul DirectAdmin \u00eenainte de rollback, export\u0103 \u0219i reaplic\u0103 manual acele date. De aceea site-urile cu schimb\u0103ri frecvente au nevoie de fereastr\u0103 de mentenan\u021b\u0103 sau write freeze la sincronizarea final\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Cel mai bun rollback este cel de care nu ai nevoie. Dar dac\u0103 ai nevoie de el, TTL-ul DNS \u0219i p\u0103strarea serverului vechi decid dac\u0103 rollbackul dureaz\u0103 minute sau devine incident public.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Probleme comune de migrare \u0219i remedieri rapide<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Problem\u0103<\/th><th>Cauz\u0103 probabil\u0103<\/th><th>Remediere<\/th><\/tr><\/thead><tbody><tr><td>Website-ul afi\u0219eaz\u0103 eroare de conectare la baza de date<\/td><td>Nume de baz\u0103, utilizator, parol\u0103 sau host gre\u0219it<\/td><td>Verific\u0103 numele bazelor \u00een DirectAdmin \u0219i actualizeaz\u0103 configura\u021bia aplica\u021biei<\/td><\/tr><tr><td>Adminul WordPress merge, dar paginile returneaz\u0103 404<\/td><td>Reguli rewrite sau configura\u021bie web server nepotrivit\u0103<\/td><td>Resalveaz\u0103 permalinks sau corecteaz\u0103 regulile Nginx\/Apache<\/td><\/tr><tr><td>Mailboxurile exist\u0103, dar utilizatorii nu se pot autentifica<\/td><td>Parol\u0103 diferit\u0103 sau clientul de mail folose\u0219te hostname-ul vechi<\/td><td>Reseteaz\u0103 parola mailboxului \u0219i actualizeaz\u0103 set\u0103rile IMAP\/SMTP<\/td><\/tr><tr><td>Emailul outbound ajunge \u00een spam<\/td><td>SPF, DKIM, DMARC, PTR sau reputa\u021bie IP<\/td><td>Corecteaz\u0103 DNS-ul, activeaz\u0103 DKIM, verific\u0103 reverse DNS<\/td><\/tr><tr><td>Certificatul SSL e\u0219ueaz\u0103<\/td><td>DNS-ul pointeaz\u0103 spre serverul vechi sau portul 80 este blocat<\/td><td>Verific\u0103 DNS \u0219i firewall, apoi reemite certificatul<\/td><\/tr><tr><td>Uploadurile e\u0219ueaz\u0103<\/td><td>Ownership sau permisiuni gre\u0219ite<\/td><td>Corecteaz\u0103 ownershipul sub utilizatorul DirectAdmin \u0219i modelul web serverului<\/td><\/tr><tr><td>Cron joburile nu mai ruleaz\u0103<\/td><td>C\u0103i vechi din mediul cPanel<\/td><td>Actualizeaz\u0103 calea binarului PHP \u0219i c\u0103ile scripturilor<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Tiparul este previzibil. Cele mai multe e\u0219ecuri de migrare cPanel la DirectAdmin nu sunt cauzate de unealta de conversie. Sunt cauzate de c\u0103i, DNS, autentificare email, versiuni PHP, permisiuni \u0219i presupuneri aduse din mediul vechi.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">C\u00e2nd s\u0103 folose\u0219ti migrare DirectAdmin administrat\u0103 \u00een loc s\u0103 o faci singur<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">F\u0103 migrarea singur dac\u0103 ai acces root, \u00een\u021belegi DNS, po\u021bi citi loguri de mail, \u0219tii s\u0103 restaurezi backupuri \u0219i po\u021bi tolera fereastra de troubleshooting. Pred\u0103 migrarea dac\u0103 acel cont g\u0103zduie\u0219te un magazin, emailuri de client, clien\u021bi reseller, baze de date de produc\u021bie sau servicii critice pentru business.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Migr\u0103rile periculoase nu sunt neap\u0103rat cele mari. Sunt cele prost \u00een\u021belese. Un site mic cu email important poate produce mai mult\u0103 pagub\u0103 de business dec\u00e2t un site static mare dac\u0103 rutarea emailului se rupe \u0219i nimeni nu observ\u0103 timp de dou\u0103 zile.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 vrei ca partea DirectAdmin s\u0103 fie construit\u0103, securizat\u0103, migrat\u0103 \u0219i verificat\u0103 de oameni care opereaz\u0103 infrastructur\u0103 de hosting zilnic, folose\u0219te <a href=\"https:\/\/www.serverspan.ro\/directadmin-management\">administrarea DirectAdmin ServerSpan<\/a>. Pentru clien\u021bii care pleac\u0103 de la cPanel, acesta este exact tipul de munc\u0103 unde ajutorul administrat \u00ee\u0219i merit\u0103 costul.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Unde se potrive\u0219te ServerSpan \u00een traseul de migrare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">O migrare cPanel la DirectAdmin \u00eenseamn\u0103 adesea mai mult dec\u00e2t schimbarea panelului. Poate \u00eensemna schimbarea arhitecturii de hosting, a nameserverelor, a rut\u0103rii emailului, a politicii de backup, a modelului de suport \u0219i a structurii reseller.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">ServerSpan poate sus\u021bine traseul de migrare \u00een mai multe feluri:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.serverspan.ro\/directadmin-management\">administrare DirectAdmin<\/a> pentru administrare de server, setup panel, hardening, troubleshooting \u0219i suport de migrare<\/li>\n\n\n\n<li><a href=\"https:\/\/www.serverspan.ro\/webhosting\">g\u0103zduire web DirectAdmin<\/a> pentru clien\u021bii care vor shared hosting f\u0103r\u0103 s\u0103 ruleze propriul server<\/li>\n\n\n\n<li><a href=\"https:\/\/www.serverspan.ro\/webreseller\">reseller hosting<\/a> pentru agen\u021bii \u0219i furnizori de hosting care mut\u0103 clien\u021bi de la cPanel la DirectAdmin<\/li>\n\n\n\n<li><a href=\"https:\/\/www.serverspan.ro\/cpanel-management\">administrare cPanel<\/a> pentru cur\u0103\u021benie pe surs\u0103, backupuri \u0219i munc\u0103 de tranzi\u021bie \u00eenainte de plecarea de pe cPanel<\/li>\n\n\n\n<li><a href=\"https:\/\/www.serverspan.ro\/linux-administration\">administrare Linux<\/a> pentru migr\u0103ri custom, reparare email, cur\u0103\u021benie DNS \u0219i depanare post-migrare<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Cea mai curat\u0103 migrare nu este \u00eentotdeauna cea mai ieftin\u0103. Cea mai curat\u0103 migrare este cea \u00een care conturile, bazele de date, mailboxurile, \u00eenregistr\u0103rile DNS, certificatele SSL \u0219i responsabilitatea de suport ajung \u00eentr-o stare stabil\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">R\u0103spunsul practic<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Migrarea de la cPanel la DirectAdmin este un proces controlat: scazi TTL-ul DNS, creezi backupuri complete cPanel, le transferi sigur, le converte\u0219ti cu unealta de migrare DirectAdmin, restaurezi conturile, verifici bazele de date, sincronizezi emailul, verifici DNS-ul, reemi\u021bi SSL-ul, validezi SPF\/DKIM\/DMARC, testezi fiecare serviciu \u0219i p\u0103strezi contul vechi cPanel online p\u00e2n\u0103 c\u00e2nd rollbackul nu mai este necesar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Migrarea nu este dificil\u0103 pentru c\u0103 comenzile sunt complexe. Este dificil\u0103 pentru c\u0103 fiecare cont poate ascunde c\u0103i vechi, reguli de mail, dependen\u021be DNS, presupuneri despre versiuni PHP \u0219i obiceiuri ale utilizatorilor. Trateaz\u0103 mutarea ca munc\u0103 de infrastructur\u0103, nu ca pe o simpl\u0103 copiere de fi\u0219iere.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 migrezi pentru c\u0103 pre\u021burile cPanel continu\u0103 s\u0103 creasc\u0103 \u0219i DirectAdmin este urm\u0103toarea ta platform\u0103, planific\u0103 migrarea corect. Dac\u0103 acele conturi conteaz\u0103, folose\u0219te <a href=\"https:\/\/www.serverspan.ro\/directadmin-management\">suport administrat pentru migrare DirectAdmin<\/a> \u00een loc s\u0103 descoperi cazurile limit\u0103 \u00een timpul cutoverului live.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>O migrare cPanel DirectAdmin \u00eencepe cu un backup complet al contului cPanel, un server DirectAdmin curat, transfer controlat, conversie cu unealta oficial\u0103 DirectAdmin pentru backupuri cPanel \u0219i verificarea site-urilor, bazelor de date, emailului, DNS-ului, SSL-ului, cron joburilor \u0219i c\u0103ilor din aplica\u021bii. Procesul sigur nu este \u201ecopiem fi\u0219ierele \u0219i sper\u0103m\u201d. Procesul sigur este o migrare etapizat\u0103, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2836,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[6767,16052,16061,16045,16057,16069,16044,16048,9088,16051,16027,16054,16053,16043,16046,16059,16056,16055,16058,16065,16068,16066,16060,16064,16062,16049,16067,16050,16047,16063],"class_list":["post-2838","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-administrare-directadmin","tag-alternativa-cpanel-2026","tag-alternativa-la-licenta-cpanel","tag-backup-cpanel-restore-directadmin","tag-backup-restore-migration-directadmin","tag-checklist-migrare-cpanel","tag-convertor-cpanel-directadmin","tag-cpmove-directadmin","tag-gazduire-web-directadmin","tag-ghid-migrare-cpanel-directadmin","tag-imapsync-cpanel-directadmin","tag-migrare-baze-de-date-cpanel-directadmin","tag-migrare-conturi-cpanel-directadmin","tag-migrare-cpanel-directadmin","tag-migrare-de-la-cpanel-la-directadmin","tag-migrare-directadmin-administrata","tag-migrare-dns-cpanel-directadmin","tag-migrare-email-cpanel-directadmin","tag-migrare-mailbox-cpanel-directadmin","tag-migrare-reseller-cpanel","tag-migrare-reseller-directadmin","tag-migrare-server-directadmin","tag-migrare-ssl-cpanel-directadmin","tag-migrare-wordpress-cpanel-directadmin","tag-panel-alternativ-cpanel","tag-pkgacct-cpanel-directadmin","tag-rollback-migrare-cpanel-directadmin","tag-trecere-de-la-cpanel-la-directadmin","tag-unealta-migrare-directadmin","tag-wp-config-migrare-directadmin"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2838","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2838"}],"version-history":[{"count":1,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2838\/revisions"}],"predecessor-version":[{"id":2839,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2838\/revisions\/2839"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2836"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2838"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2838"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2838"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}