Hodi in Togo for migrating WordPress and retaining email

Who Hodi may suit

This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.

Plans, prices and renewals

Prices retain the market, currency and billing period described in the French source. Translation does not update a commercial quote. Confirm the final price, taxes and options before ordering.

Languages and support

Website and documentation

Website and help in French; English version available.

Control panel

cPanel. Languages actually enabled on the account to be confirmed.

Support

French documentation and support channels. Written help also in English. Human support in another language to be confirmed.

Hodi in Togo for moving WordPress without moving email

Hodi displays a Site Pro offer for Togo, with a server advertised in Lomé, cPanel and WordPress Toolkit Deluxe. In this profile, a fictional association wants to move its public WordPress pages. It keeps office email, volunteer mailboxes and the domain with its current operator. The change must therefore affect site destinations while preserving records that deliver and authenticate email.

Two errors may look alike on switchover day. If the main name points to the new server but an old IPv6 address remains published, some visits may still reach the old site. If a nameserver change omits email records, pages may work while email takes the wrong route. A home-page screenshot rarely distinguishes these situations.

The exercise compares DNS snapshots in memory. It uses fictional domains and addresses reserved for documentation. The profile distinguishes the production zone, backup copies and WordPress operations. Prices and terms concern Site Pro for Lomé even though the provider sells other ranges in several countries.

Price Site Pro in CFA francs and date the notice period

The Site Pro page for Togo displays 14,990 CFA per month excluding VAT, in BCEAO CFA francs (XOF). Twelve months at this constant rate total 179,880 XOF excluding VAT. This total budgets the year. The headline price and FAQ describe monthly payment, while duration and price of the chosen cycle must come from the contract. No separate renewal rate or setup surcharge is established by the offer page. Have the first invoice, possible fees and renewal price specified. A domain is listed in .tg, .africa or .com extensions. Confirm the selected extension, inclusion duration and amount due when it ends. For the association, an already owned domain can stay with its registrar.

The legal notice assigns the site to Hodi SAS, registered in Réunion. The footer states that applicable VAT is determined when ordering. The Togolese Revenue Office specifies a standard rate of 18%. If it applies to a hosting invoice of 14,990 XOF excluding VAT, the calculation gives 17,688.20 XOF before billing rounding, or 212,258.40 XOF over twelve months at the same price. This calculation does not establish VAT the seller will apply to a particular profile. Have hosting, domain, any assisted restoration and tax treatment of each line distinguished. The general service terms name XOF among bank-transfer currencies.

The commercial FAQ presents the offer as monthly with no commitment. The general terms require fifteen days’ notice for monthly billing, two months for other contracts and allow price revision at the anniversary. The help center distinguishes hosting cancellation from disabling domain auto-renewal. Keep a calendar by service. If the association wants to stop a service after rehearsal, it must allow time to export data and then respect the applicable notice period.

Distinguish account resources and copy residency

Site Pro displays up to five domains, 50 GB disk, one hundred email addresses, four vCore and 4 GB RAM. Space is advertised for the account offer. Domain count does not create five separate memory and disk reserves. If the association also hosts its event site in the account, images, caches and temporary copies add to sizing. Ask about inode, process, I/O and PHP limits applying to this configuration. Redis or AccelerateWP does not replace this check. A cache helps public-page reads. The editor, imports and some forms continue triggering dynamic processing.

Hodi advertises this offer’s server in a Tier III data center in Lomé. The offer page also advertises a daily Lomé copy with thirty-day retention, a backup in the ECOWAS zone and multiple data centers. Current terms and the Togo DPA specify that granular backups of West African web hosting occur nightly in Lomé, with thirty-day retention unless the quote states otherwise. General help describes a web copy in a second center outside the country. For Site Pro in Togo, geographical provisions in the profile, DPA and article 22.3 agree on Lomé. If location determines selection, have each copy and any separate service processing data abroad confirmed in the quote.

The terms also describe an internal nightly recovery copy retained seven days and inaccessible to customers. The granular copy allows targeted online restoration and excludes some temporary or cache files. Hodi intervention on request is listed at 79 EUR excluding VAT in article 22.3, with exceptions for VIP and CYBER+. After cancellation, article 26.3 provides for deletion of this range’s copies after thirty days and distinguishes manual recovery at 79 EUR excluding VAT per 500 GB, before any fees. Export data before canceling.

The fictional case retains its email provider. Even though one hundred addresses are advertised, they are outside the chosen migration scope. Prepare an inventory showing, for each domain, what serves the site, receives email and authenticates sends. Check forms’ current entry point. A WordPress-hosted form may use the current email provider or another relay depending on configuration. Correct DNS resolution validates only traffic direction. The sending server and destination configured in the application still need checking.

Separate the panel, WordPress and AI connector

The Togo website and cPanel guide exist in French. English offer and help versions are published. The panel is cPanel. Screenshots and sections help prepare operations, while account-enabled languages and human English support remain to be confirmed. Hodi publishes support-request channels and network status. Consulted sources set no guaranteed restoration time for the standard package. Have the channel and useful response time for a production outage recorded.

Site Pro advertises WordPress Toolkit Deluxe, PHP environments and MySQL databases, plus PHP settings through cPanel. To take over an existing WordPress site, list core, theme and plugin versions, then choose a PHP version they actually support. The panel supplies administration tools. Public pages do not describe host validation of business plugins or forms after every update. Agree who checks these functions.

Hodi presents an MCP connector for compatible assistants and mentions Hodifly in Site Pro. The connector acts according to account permissions, including services such as hosting or domains. Current terms describe revocable access and a change log. Retain this log if authorizing a change and remove the token after intervention. The commercial profile quantifies no included WordPress generation credits. For the association’s switchover, the DNS inventory can be compared without a connector. A team using this feature later should separate read permissions from modification permissions and subject any DNS change to human validation. Do not paste credentials, mailbox contents or member data into an assistant request.

Prepare the backup and site switchover

Before any change, export WordPress files, database and configuration at a consistent point. Keep an independent copy and read table names and the media list before relying on the archive. Also export the current DNS zone from its authoritative manager or obtain it from the administrator. Record current values and TTLs for the main name and www. In the same sheet, separate MX records, TXT records related to SPF, DKIM and DMARC, and mail-host addresses if those names are in your zone. Retain autoconfiguration entries and service validations outside the change scope. This sheet is your rollback plan if a web record no longer resolves to the correct destination.

Hodi advertises free incoming migration of files, databases and mailboxes. Here email stays in place: exclude mailbox transfer from scope and have the preview method specified. The registrar, authoritative DNS servers and email service may be three different providers. For shared hosting, article 2.1 makes the guarantee conditional on DNS servers communicated by Hodi. The Let’s Encrypt certificate also requires pointing to the IP supplied by Hodi. On rehearsal day, compare the zone export with the record. Check whether the site uses a CDN, proxy or CNAME records to a platform. The exercise shows a case where the main name has A and AAAA and www is its alias. Another topology requires checking its own targets.

If retaining current DNS, have compatibility and guarantee limits confirmed by Hodi, then compare only relevant web A, AAAA or www changes. If delegating DNS to Hodi, prepare and review the new zone before delegation. Keep MX, authentication entries and email targets with the current operator. If DNSSEC is active, coordinate its continuity with the registrar and both zone managers.

If the current DNS provider exposes TTL management, you can reduce the TTL of web entries to change in advance. Wait at least the previous TTL duration before relying on the lower value. Keep email timings unchanged when routing remains identical. In cPanel, Domains, Zone Editor, Manage provides zone access when enabled. A change in this panel has a public effect only if the zone is actually served by authoritative servers. Before changing anything, identify the real manager and keep a capture of the original zone.

Practice switchover in two fictional DNS zones

The fictitious scenario compares three candidate zones and checks preservation of email entries. — Illustration by BlogPasCher.Open full-size illustration ↗

The file EXERCICE-HODI-TG.cjs runs with Node.js alone. Run node EXERCICE-HODI-TG.cjs in the extracted ZIP directory. Example IPv4 and IPv6 addresses are reserved for documentation and names are fictional. The script performs no DNS resolution and writes no zone. It simulates neither delegation, DNSSEC nor certificate issuance. It compares expected web-address lists with an inventory and verifies that five protected groups remain equal to the reference. The table RESULTAT-HODI-TG.json records web differences, protected-group drift and the verdict for each candidate.

In “Forgotten IPv6,” A changes but AAAA still leads to the old server in the model. The result flags AAAA. In “Incomplete zone,” both web addresses are correct but MX and DKIM groups are missing. The result flags them separately. In “Targeted switchover,” both web addresses match the destination and protected entries remain identical. Web rollback restores initial addresses without touching protected groups. Assertions cover all four results, including rollback, so a seemingly correct switchover cannot be validated without comparing other entries.

To adapt the method, first create a table for every name in your zone and list type, target, any priority and TTL. Model keys group certain TXT records for teaching purposes. SPF, DKIM and DMARC are not three different DNS record types. DKIM may also take the form of a CNAME depending on provider. The script validates neither real-record syntax nor email delivery. To use it as a review aid, replace values in a copy while retaining the same comparison format. Separately verify TTL, zone consistency and application tests. The expected result is a short, readable list of authorized web changes and entries that must remain stable.

Test both workflows from a private copy

Restore WordPress to a private destination with a separate database. Verify that the copy sends no real email and triggers no payment or external task. Open the home page, a recent image, a PHP-dependent page and a form submission to a test mailbox. In WordPress administration, check that site and dashboard URLs match the selected preview mode. If the test address differs, make any copy URL changes with a serialized-data-compatible tool. If images remain absent, distinguish a missing file, old address and server block.

Prepare checks after any zone publication by the responsible team. For the Web, separately record the A target, AAAA presence and target, www behavior, certificate and redirects. If the new infrastructure has no IPv6, discuss removing the old AAAA as an explicit change rather than leaving it pointing to the old server. For email, compare MX and authentication entries with the inventory. Then test reception and form submission between authorized addresses. A successful form does not prove the office mailboxes still receive all messages.

If testing reveals a web problem, restore preserved web values and keep email on its reference zone. If delegation changed, keep both complete zones during transition and coordinate nameserver and DNSSEC rollback with the registrar. If the problem affects email, compare actually published records before touching mailboxes or resetting a password. Keep both environments while DNS caches refresh and note any submissions appearing on either side.

Decide before changing records

Site Pro matches the scenario if the association wants a server advertised in Lomé, has a way to preview the site and can retain email management with its current operator. The acceptable model candidate changes both web addresses and retains protected entries. Before the real change, appoint a zone administrator, WordPress administrator and person checking reception. Give each specific observations and a decision time. Assemble the DNS inventory, backup point and means of contacting providers at that time.

Authorize switchover if the private copy works, the old zone is saved, email entries are identical and the new target is confirmed for each address family used. If the target has no IPv6 or www is not an alias, revise the written plan and rerun an adapted comparison. If the project requires all copies to remain in a specific region, pause the commercial decision until backup scope is confirmed in the quote. For a project without that requirement, still verify how to retrieve database and files independently of opening a ticket.

Rollback restores previous web records and preserves email. It takes time when caches retain the prior answer. An error found after submissions may also require WordPress data reconciliation. Define the latest point at which the team can return to the old destination, the threshold triggering that decision and when the historical copy will be removed. The budget must remain readable at selection time: displayed monthly price, billed tax, expiry, domain renewal and restoration terms must correspond to separate lines.

Prepare your site

• 25 WordPress backup tools by recovery need
• WordPress images returning 404 after migration: repair files and addresses
• WordPress migration, staging and imports: choose the right tool
• Download the DNS switchover exercise