Conexcol Cloud in Colombia for WordPress and WooCommerce

Who Conexcol Cloud 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 website. Spanish knowledge base with some English articles.

Control panel

cPanel, documented Spanish labels and some tool names in English. Check other enabled languages.

Support

Spanish advertised, tickets, chat and local telephone numbers. Confirm other languages.

Conexcol Cloud in Colombia: schedule a WordPress import

Conexcol Cloud offers cPanel hosting in Colombia that supports WordPress and describes resources allocated per account. A fictional store in Medellín imports a catalogue while WordPress creates thumbnails. Each operation may succeed separately and cause a problem when both need the same processing slots.

The decision concerns scheduling before the price of a higher plan. The local exercise compares a schedule with overlapping processing against one that postpones image generation. The work remains identical. The model gives the peak number of simultaneous tasks and shows whether the second schedule respects the chosen ceiling and end time.

The profile separates promotional price from renewal, plan capacities from site settings. It identifies the access needed to repeat the import, read records and restore content if the working window is insufficient.

Compare the amount charged and renewal in pesos

The public table consulted on November 10, 2026 displays a 30% discount for new customers’ first period. The card expresses a monthly price for comparison, then gives the period amount and renewal. The “monthly cost” column may vary by one peso with rounding. For the budget and internal purchase order, copy the period total and record how many months it covers. Offer boxes give Colombian-peso prices recorded outside the ordering process.

V3’s initial payment is 54,136 COP lower than V2’s, but V3 covers twelve fewer months. At unchanged displayed prices, adding the first V3 period and its first renewal gives 1,197,951 COP for twenty-four months. V2 displays 547,410 COP for its first period of the same duration. The comparison therefore concerns two resource profiles and the payment schedule. If V2 suffices for normal traffic but lacks headroom for occasional processing, the frequency and cost of moving that processing enter the decision.

The Colombian tax authority lists hosting among services excluded from IVA under Article 476. The provider advertises electronic invoicing in Colombian pesos. Verify each service’s treatment on the invoice. On a combined quote, have hosting, domain and any services separated before budgeting the invoice. Retain amounts in the original currency and compare lines covering the same duration.

The general terms describe a written cancellation request submitted to Conexcol by an authorized person. Before subscribing, record the channel applicable to your contract, effective notice date, renewal and treatment of prepayment. Ordering, domain renewal and leaving hosting are separate operations. If the import cannot be repeated before renewal, also set a decision deadline allowing time to validate copies.

Read resources and data location

Conexcol presents its elastic sites as cPanel accounts with isolated resources under CloudLinux, hosted on infrastructure in Colombia. The table gives CPU, memory and storage allocations. Consider resources at account level, especially if the store shares it with a brochure site or another installation. Medellín is the setting for our scenario. For a contract requiring a precise city or zone, record the primary processing country and site, backup zone and any replica scope separately. SSD disk space does not measure concurrent entries or writes per second.

Moving from V1 to V2 adds RAM and disk while retaining one vCPU. If thumbnail generation is mainly CPU-limited, increasing memory alone does not explain a gain. A large CSV may instead expose a PHP limit or account memory constraint. Free space may become the constraint while original media, resized variants and a temporary copy coexist. An import and visits may share the same ceiling even if each task works correctly without the other.

For your quote, request a line for each useful resource: entry processes, process count, I/O and IOPS, inodes, account memory, editable PHP settings and actually available space. The standard table’s “Ver” details display 20 to 140 EP for V1 through V7 in increments of 20. NPROC runs from 50 to 350 in increments of 50. The exercise uses fictional capacity independent of these figures. For HTTP or console processing, identify the limit that actually rises during the trial. Specify whether the trigger is an HTTP request, scheduled task or console operation. CloudLinux documents separate counters and notes that LiteSpeed integration mode changes how some entries are counted. Keep measurements separate in the log. A RAM-related incident will then not be attributed to the number of imports started in the same minute.

Define WordPress, languages and AI

The WordPress page describes installation through cPanel, LiteSpeed and LSCache. The provider’s cPanel documentation also details Softaculous and WordPress management features. The table advertises MariaDB 11.4 and PHP settings accessible according to the offer. Allocate responsibilities before importing: who validates plugin compatibility, updates the copy, clears cache and decides on rollback. Hosting support can document account resources, while validating catalogue prices, taxes and variations remains work on the store.

Conexcol’s sales site and cPanel guides are in Spanish. Panel illustrations show Spanish cPanel labels while retaining some English tool names. Public help also includes English articles. Confirm other languages enabled on the account. For a bilingual team, prepare a glossary of sections needed for import and restoration, then confirm interface language on delivery. Public channels include tickets, chat and local telephone. The site and guides help prepare a request in Spanish. Guaranteed support in another language remains to be confirmed before making it a contractual criterion.

Conexcol advertises free assisted inbound migration in its migration offer. List sites, databases and mailboxes to move and check which are covered in the quote. Retain access to old hosting until the copy responds at a preview address, media displays and email has a separate workflow.

The cPanel offer associates AI with Imunify360 threat detection. Treat that under security. The table establishes no WordPress content-generation credits in V1 through V7. Conexcol also documents Sitejet Builder in cPanel. Its generator produces a new site subsequently edited in Sitejet. It may suit a new brochure site, while product imports happen in the WordPress store. A catalogue import can remain entirely deterministic: SKUs match rows to products, the validated CSV defines changes and results are checked on a small sample. Text or image generation changing this test’s data would introduce a second variable while the store is trying to isolate scheduling effects.

Prepare copies and rollback before importing

The provider documents JetBackup in cPanel, where copies offered by the account can be restored or downloaded. The table advertises three recent daily points, one from the last week and one from the last month, with targeted restoration of files, databases or email from cPanel. Check points visible in the account. After a hosting account is deleted, the SLA allows up to thirty days to request a copy. If the plan has already ended, recovery requires at least the equivalent of one month of the plan under the SLA. For an active account, record actual frequency, oldest available version, backed-up items, granularity and recovery time. Record visible dates and components before using a point for post-import rollback.

Prepare a dated recovery point before the change. Export database and useful files at the same logical moment, record WordPress, WooCommerce and plugin versions, then put a copy outside the space to be restored. Verify that it opens and contains necessary tables, media and configuration. A product CSV inventories the catalogue. The database also contains application relationships, settings and writes. A full restore performed too late can overwrite orders received after the recovery point. During rehearsal, measure the time until a product page, variation and its image become usable again. Before production, agree how to preserve later orders if rollback becomes necessary.

Keep a recovery sheet with each archive’s name, capture time, restored scope, observed duration and person approving reopening. A database restore may restore prices while media added later remains on disk. A files-only restore may leave database references to vanished objects. Testing must therefore check several product/image pairs, including a product whose thumbnails were changed by the batch.

Practice choosing a processing window

The fictitious scenario compares three thumbnail start times. — Illustration by BlogPasCher.Open full-size illustration ↗

The supplied exercise models a fictional ceiling of three simultaneous tasks. It reserves one slot for the store from minute zero to minute twenty and places two catalogue batches from zero to twelve and zero to nine. Thumbnail work lasts seven minutes. The hypothesis assigns the same load to every task and fixes durations so that only thumbnail start time changes. The program uses in-memory data, Node.js and its built-in assertion module. It requires neither a WordPress installation nor network access.

After extracting the ZIP under “To prepare your site,” run node EXERCICE-CONEXCOL.cjs. The file RESULTAT.json contains recorded output. For each scenario, the program lists windows with constant task counts. A task finishing at nine frees its slot for another starting exactly at nine. A task starting at three can exceed the threshold even if everything seemed compatible at the beginning of the twenty-minute window.

The first scenario starts thumbnails at three. It reaches four tasks from minute three to minute nine and finishes on time but exceeds the ceiling. The second starts at nine. It stays at a maximum of three tasks and completes all work by twenty. The third starts at fifteen. The peak remains three, but the last task finishes at twenty-two. The only acceptable scenario in this model is therefore starting at nine. Assertions enforce both conditions to prevent approving the third scenario based only on its peak.

Then open the original diagram supplied. It represents the same occupancy as bars and distinguishes the threshold from the deadline. To extend the exercise, change the duration of the batch that was supposed to finish at nine in a copy and rerun it. Reference-example assertions will flag the change if the peak or verdict changes. Then adjust expectations for the new trial and justify the chosen delay. The model’s three slots are a teaching convention. To measure an account, record task type and counters observed during rehearsal. The model answers the specified scheduling problem, while observation answers the actual-capacity question.

Repeat the import and observe resources

On a private copy, take a small CSV containing a simple product, a variable product and a known image. First export the existing sample. Normalize encoding and compare columns WooCommerce will map. For an update, use existing SKUs or IDs and explicitly decide how unmatched rows are handled. Variations may follow rules specific to the version and mapping. Try a visible stock or price change, then open the product and variation from the store. Import results and excluded rows allow correcting the source before the next batch.

First check whether your tool can separate catalogue import from thumbnail generation. If linked in your workflow, measure them as one task, then reduce batches or stagger other work; the model supplies no WooCommerce setting to separate them. If separable, start with the import alone, thumbnails alone, overlap and the staggered window. Record start time, row count, errors, response time on a reference page and reached limits if the account exposes them. Retain the same data version and reset the copy to the same initial state between trials, especially cache and generated media. Otherwise, the first pass has already incurred file-creation costs and the second appears less demanding for that reason alone. Treat a batch finishing with long requests and errors as a failure even if it meets the schedule.

Also record accepted, rejected and incomplete row counts and the last processed identifier. If a task is interrupted, reconcile this record with the visible state before rerunning. Replaying only failed rows is preferable when the update has been verified as reproducible and ancillary processing does not trigger twice.

Decide between staggering tasks and changing plans

For the fictional store, retain the staggered scenario as the first candidate. Authorize the change only if a copy trial shows both batches finishing within the window, limits remaining below the agreed threshold and reference pages staying usable. Set a response-time threshold and error rate before the trial according to what the store can accept. Script success decides only the synthetic schedule. Choosing to operate on a plan depends on measured real workloads and rollback capability.

If overlap alone triggers incidents, schedule thumbnails after the short batch and keep headroom for a retry. If an isolated batch already fails, first identify the resource and measurement establishing the cause. More memory may help processing that stops for lack of RAM. A CPU, I/O, EP or inode requirement calls for confirmation of the corresponding value on the next plan. Ask the cost of changing mid-period, its effect on the renewal date and whether returning to the original plan is possible. Record answers in the budget alongside first-payment and renewal figures.

Final approval must name a window, the person initiating work, the largest tested batch, the abort deadline and restoration method. A repeated peak with isolated tasks, an unverifiable copy or a recovery window incompatible with ongoing orders suspends the import. Keep the dataset and trial log to test a different WooCommerce version or plan later using the same reference items.

Prepare your site

• 25 WordPress backup tools by recovery need
• WooCommerce CSV import: update the right products without creating duplicates
• WordPress migration, staging and imports: choose the right tool
• Download the import-scheduling exercise