Bolivia Hosting in Bolivia: WordPress prices and site migration

Who Bolivia Hosting 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

Spanish on the public website, portal pricing table and terms consulted.

Control panel

cPanel. Spanish is documented by the publisher; check activation and the portal.

Support

Tickets for technical requests. Email and Bolivian WhatsApp for general inquiries. Confirm actual languages and response times.

Bolivia Hosting for migrating WordPress while preserving email

A small office in Santa Cruz wants to move its WordPress site to annual hosting in bolivianos while keeping business email with its current provider. Bolivia Hosting offers three small plans with cPanel, SSL, a MySQL database and advertised weekly backups. The domain can point to the new site while email receipt and authentication continue to depend on other records. Acceptance testing distinguishes these operations and plans to keep the existing DNS zone as long as it meets the office’s needs.

This profile examines plan capacity for a lightweight brochure site and the cost to expect at the end of the first year. The practical case tests a fictional DNS inventory. Two variants correctly point the web page, but one loses email records and the other leaves an old web address in place. A variant preserving both services serves as the reference before switching over. The office can then divide the steps between the WordPress administrator and the person familiar with the email account, with an initial state both know how to retrieve.

Budget for the annual service and its renewal

The WordPress range displays 90, 220 and 290 bolivianos per year, currency code BOB. The product page also presents struck-through amounts labeled as previous prices. The public store repeats the current amounts for an annual cycle. The struck-through amounts do not document the following year’s price. The terms allow future price changes with reasonable notice and protect periods already paid for. The office can therefore budget for renewal and confirm the amount when the notice arrives.

The terms describe prices as final unless stated otherwise and declare that the provider does not collect country-specific local taxes. This wording describes the published pricing policy. The Servicio de Impuestos Nacionales states a general IVA rate of 13%. The office must obtain the invoice corresponding to its account holder and the proposed cycle. This profile retains displayed prices and does not add calculated VAT.

Renewal is paid manually, after which the customer submits proof for validation under the terms. The first notice is advertised at least twenty-one days before the due date. For a migration, list hosting, the already-owned domain and the email service separately. The homepage specifies that the number of domains allowed in a plan does not include their purchase. This project’s cost therefore depends as much on keeping email and the domain with their current providers as on the 90 to 290 BOB for hosting.

Read quotas and size the brochure site

The three WordPress plans include one MySQL database, one permitted domain, one subdomain, SSL and cPanel. The range publishes storage capacity and monthly transfer quota. A single database does not establish whether a supported clone can be installed. Check with the host whether a temporary environment can use a separate database. Otherwise, a local or external copy remains easier to separate from the live site.

To choose, record file and database sizes, actual monthly usage and usage during the busiest months. A 700 MB site may fit the first plan while idle but become too tight for a local archive copy or extra photos. A brochure of several megabytes downloaded during a campaign may instead hit the traffic limit first. Maximum storage and transferred volume must remain separate lines in the capacity budget. Included mailboxes can remain unused if email continues elsewhere. The page does not specify account behavior when the transfer quota is exceeded.

Shared-hosting terms set a ceiling of 400,000 inodes and limit sustained consumption to 20% of server resources for CPU, RAM and processes. They do not, however, provide a quantified vCPU or memory allocation specific to these three plans. They locate infrastructure in data centers in the United States. The offer targets the Bolivian market, while the exact assigned location and backup-copy location remain to be confirmed. For an office already using external email, also check where the site form sends its requests.

Distinguish WordPress, support and languages

The range is presented as hosting suited to WordPress and other CMSs. The terms assign WordPress, plugin and theme updates to the customer and exclude CMS administration from standard support. The team taking over the site must therefore know the required PHP version and modules, check scheduled tasks and retain a WordPress administrator login that works on the copy. The range page confirms cPanel and SSL. Check offered PHP versions, installer availability and update automation for the prospective account.

The public website, catalogue consulted and terms are in Spanish. cPanel documents configurable languages, including Spanish, with the setting location depending on version. Languages actually available in the account, portal and support replies remain to be established. Customer-area tickets are reserved for technical requests and account-specific questions. Under the terms, email and Bolivian WhatsApp serve general and sales inquiries. Response language for each channel and processing hours have not been verified in practice.

Bolivia Hosting’s table and terms document no AI WordPress site generator, integrated administration assistant or credits associated with these plans. The provider’s domain name helps avoid confusion with Bolivia Host, a separate company whose catalogue includes other products. For this project, the operations to plan are site export, restoration in a test environment and verification of addresses and forms. Generation features are not part of the selection criteria.

Prepare the site copy and DNS inventory

Prepare a copy of the files and database, then verify that it opens in a test environment. Record PHP and WordPress versions, the certificate, addresses used, pages to test and how the form sends messages. The range advertises weekly backups. The terms generally present them as a best-effort service and allow storage on the same infrastructure or additional storage. Confirm retention, backed-up items, possible recovery cost and restoration time. The terms mention assistance with simple migrations when feasible. They do not guarantee complete recovery of the site and email.

In the account currently hosting the authoritative DNS servers, export or copy the zone. For every entry, keep its name, type, value and TTL, which indicates how long a resolver can retain the response. Also record which provider can change delegation and, if DNSSEC is active, the corresponding configuration. The exercise’s switchover keeps the nameservers. It compares the domain and alias web records with email entries, including MX and the SPF, DKIM and DMARC entries used by the office. Also check whether a server name used by MX depends on an address the team plans to change.

In cPanel, Domains → Zone Editor → Manage provides access to records if the host has enabled the menu. A zone present in cPanel may serve only the account’s local operation. Prepare public changes in the interface of the provider answering for the effective zone. Identify that interface from the registered nameservers and keep a copy before proposing the change.

Practice a switchover limited to web records

The exercise distinguishes switching the website from preserving mail. — Illustration by BlogPasCher.Open full-size illustration ↗

After extracting the ZIP, open a terminal in the directory and run the following command.

The fictional zone contains an A record for the old IPv4, an AAAA for the old IPv6, a CNAME alias for www, an MX and three TXT entries for email. The exercise’s destination provides a new IPv4 and no IPv6. The expected zone replaces only the A entry and removes the old AAAA that would still point to the previous server. The alias and four email entries retain their values.

The first candidate recreates only the two necessary web entries, A and CNAME. Four email entries are missing even though a browser can display the new brochure site. The second candidate retains the zone but replaces only the A entry. It contains an obsolete AAAA, leaving two possible responses depending on the address used by the client. The third applies the two planned web changes and preserves the rest. The output reports four missing records, then one unexpected entry, then no differences. The expected result is in RESULTAT-BOLIVIA-HOSTING-BO.json.

The program compares records with their values and TTLs, regardless of list order. It connects to neither a resolver nor an administration interface. The zone, names and addresses are reserved for demonstration. In a copy of the exercise, change the MX destination in the third candidate and observe that the expected value becomes missing and the different value appears as unexpected. For a real project, determine the correct AAAA handling after confirming the new host’s capabilities and other services using the same name. If the provider supplies an IPv6 to use, the goal becomes replacing the old address with the new one. The exercise checks the planned inventory for a particular case. Actual resolver, certificate and SMTP server behavior requires separate acceptance testing.

node EXERCICE-BOLIVIA-HOSTING-BO.cjs

Repeat web and email acceptance testing

Before the public change, load the WordPress copy at a supplied test address or in an isolated environment. Check the homepage, two representative pages, downloads, administration access and the intended handling of a form. For final validation, include the domain name and www if previously used. Check the expected redirect and a valid certificate for names that remain accessible. When the certificate can only be issued or tested after the DNS update, plan who will act and which result triggers rollback.

After confirming destinations with the provider, apply only the approved differences in the authoritative zone. Reread web and email records, then check from an external connection that the domain serves the new site when the DNS cache refreshes. For email, have receipt and a reply checked through the existing email service. In the WordPress form, also check the intended sending path and receipt in the destination mailbox. Preserving MX confirms the advertised inbound route. It does not by itself validate WordPress sending.

If cPanel handles local routing, check Email → Email Routing for the domain when the provider has enabled this interface. Ask support to confirm a setting consistent with an external provider and check delivery of a message from the site. cPanel’s automatic detection relies on its local zone and does not independently recheck public DNS. The final record separates web results, external email results and form-sending results. An error in one column can be analyzed without invalidating the other checks.

Decide on departure and keep a rollback path

Básico may suit a brochure site whose size and traffic have been measured and whose email remains separate. Económico primarily increases transfer and storage headroom. Especial remains limited to one database and targets a brochure site with slightly more files, without providing a second WordPress environment. Before choosing, the office can record its busiest month and headroom for document distribution, then check how the provider handles a reached quota. If preparing the clone takes space, perform that step outside the account that will host the site.

A certificate failure, essential-page failure or form failure is grounds to postpone or roll back. Keep the old site accessible and record the original pair of web records before the change. If rolling back, reapply the previous web values according to the recorded state, then wait for cached responses to expire and recheck both names. Preserve email records unless a possible email incident warrants separate intervention by the email provider. If forms were received during the transition, retain delivered messages and make a record before closing either site.

To leave the service, the terms require cancellation before the due date through the specified channels. In case of nonpayment, they announce suspension after three calendar days and possible deletion after thirty days. That latter period is not a guaranteed window of file access. Export and verify the external copy before the deadline. Also check which account holds the domain and public zone, and prepare the domain transfer separately if the office needs it. After switching over, the site owner can sign off the record with the person responsible for email once the brochure site, mailboxes and form have passed their respective checks.

Prepare your site

• WordPress migration, staging and imports: choose the right tool
• HostingMontevideo or mCloud for connecting WordPress with third-party DNS?
• WP Mail SMTP or FluentSMTP: choose email routes
• Download the DNS switchover exercise