TransIP or Combell for moving WordPress without duplicate notifications

Move a form that may already have sent a message

An association is moving its WordPress site to a new host. The contact form records each inquiry and prepares a notification for the team. During acceptance testing, inquiries are fictitious and messages must stay in a capture mailbox. At cutover, only one instance must be able to process new messages. A decision is also needed about a notification still appearing in the copied queue when the relay may already have received the message from the original site.

The choice between TransIP and Combell concerns the means of controlling this transition. The first confines interventions to WordPress and its panel. The second also documents file and database access for managed WordPress. This difference matters if the transport, queue or attempt register is not visible in WordPress administration. It does not establish that either product automatically stops the clone’s outgoing messages.

The expected outcome is a recorded decision. Acceptance testing must send nothing to a real recipient. An inherited attempt must have an actionable status before being retried. Finally, the site designated after cutover must produce only one notification in the planned test. A form displaying its confirmation may complete the first link in the journey while leaving a queue blocked or a recipient incorrectly configured.

Separate what the form, relay and mailbox prove

Give the submission a stable identifier. Associate it with the expected notification and recipient role, such as team or visitor. If a form provides two different notifications, they have two distinct identifiers. Keep these identifiers when copying the queue and avoid using the visitor’s address as a key. The same visitor may submit two legitimate inquiries. A single inquiry may also trigger several expected emails.

Record separately the submission write, the processing request sent to WordPress, any relay response and receipt in a control mailbox. The wp_mail documentation states that a success value does not guarantee receipt by the recipient. If the relay accepted the content but the connection breaks before the application reads its response, the outcome may remain uncertain within WordPress. A retry can then create a duplicate.

Before copying, identify the mechanism sending messages. The form may call WordPress directly, store a job in the database or use an external service. Each path requires proof of isolation. A test mailbox alone does not disable a plugin that communicates directly with an email API. Keep the real sending system disabled in acceptance testing until all paths are identified.

TransIP Managed WordPress and control through the dashboard

In the Netherlands, the starting plan examined advertises 20 GB of data, one test environment, five 2 GB mailboxes, 64 MB of Varnish cache and fourteen days of backups. The testing guide describes a main-site copy on a subdomain, the ability to set a username and password, refreshing from the public site and a command replacing the public site with the test site. This test subdomain is part of the tool. It should not be taken to imply unrestricted access to additional subdomains.

Managed WordPress is administered through the dashboard. TransIP states that there is no direct SFTP or SSH access, file manager, direct database administration or cron task configuration in the panel. These limits do not apply to the entire brand. Its unmanaged WordPress Hosting plan documents SFTP, SSH and phpMyAdmin. If your check requires a configuration file or SQL access, verify the exact range before selecting Managed.

The migration guide offers a plugin for WordPress Hosting and Managed WordPress plans. At the destination, make sure the form, its log and the notification-suspension mechanism remain controllable from WordPress. TransIP’s outgoing email guide asks users to check the From domain, including when sending from a subdomain. It also covers domain authentication settings and advises against adding an SMTP plugin to troubleshoot a form. If you choose a separate transport, check its scope on this plan and any paths bypassing it. The guide does not demonstrate that Managed disables real transports on a copy.

The documentation and process consulted are in Dutch. TransIP advertises written support from 08:00 to midnight on weekdays and 09:00 to 19:00 on weekends and public holidays, with a stated response within one hour during opening hours. Help mentions telephone support for domains and web hosting on working days from 09:00 to 17:00, using a panel code. Confirm telephone coverage for this plan and the agent’s language. The support page states that agents do not directly configure customer services.

Combell Business and access to traces outside WordPress

In Belgium, Managed WordPress Business displays 50 GB of web space, one test environment, daily backups retained for fourteen days and fifty 25 GB mailboxes. The card mentions a 1 GB database. The detailed table states two MySQL databases of 1 GB each. Size the migration for 1 GB per database and confirm how the plan counts the test copy. Help explains how to protect acceptance testing with a username and password, then start from a site copy or backup. This protection limits access to the clone’s interface. It does not by itself control the messages the clone can send.

The managed WordPress setup guide states that files are accessible via FTP after creating a user, and phpMyAdmin is accessible from the WordPress overview. The migration guide also describes the file manager and migration plugin. These paths give the operator additional means to examine files or a database queue. Exact permissions on the Business test environment, the encrypted protocol offered and relay-log access remain to be checked. The acceptance-test account should see only data necessary for its role.

For shared hosting, Combell’s guide explains that PHP’s mail function may send through the shared relay without message authentication. It documents configuring authenticated SMTP transport if the application needs it. Confirm that the selected transport and its traces are usable on Business staging. Included email mailboxes prove neither isolation of clone notifications nor visibility of an attempt in the relay log.

The package advertises continuous support. The card also mentions Butler, while the services table reserves this transfer for the Professional and Expert columns. Confirm Butler’s inclusion and scope for Business before making it a cutover condition. The help page lists telephone and email, plus panel chat from 09:00 to 17:00. Pages are available in French, Dutch and English. Confirm the channel and language for the cutover window. If a provider prepares the copy, assign destination checking, task reconciliation and notification reactivation separately.

Calculate the first two periods in euros

TransIP’s public page displays 3.99 EUR excluding VAT per month for the first three months for the 20 GB plan, with 12.50 EUR excluding VAT per month as the displayed regular price. At these references, three promotional months and nine regular months total 124.47 EUR excluding VAT over twelve months. Twelve months at the regular rate total 150 EUR excluding VAT. At the standard Dutch 21% rate if applicable, the examples are 150.61 EUR including VAT and 181.50 EUR including VAT, rounded on each total. Prices and rounding on individual monthly invoices may differ.

TransIP’s terms specify a one-month term renewed for one month for services outside categories with specific durations, such as domains and certain certificates. Help requires one month’s notice to cancel through the account. Under the terms, recurring fees are billed monthly in advance. The cited card excludes VAT, and the price presented to an individual may include VAT. Record the next service renewal date and actual billed period. The regular 12.50 EUR price is the one recorded on the page and does not fix future invoices. The twelve-month example is for budget comparison.

Combell Business displays 7.48 EUR excluding VAT per month in the first year and 19.99 EUR excluding VAT per month as the crossed-out regular price. Twelve months total 89.76 EUR excluding VAT and 239.88 EUR excluding VAT. With Belgian VAT at 21% if applicable, the references are 108.61 EUR including VAT and 290.25 EUR including VAT. Price the domain offered free in the first year separately for subsequent periods. Article 3 of the general terms specifies one year by default, renewal for the same duration and cancellation notice no later than one month before expiry. Article 4 provides by default for billing the year at the start of the period. Confirm the renewal amount and associated services before selecting the plan.

Prepare the destination before starting processing

Keep the old site in charge of sending during preparation. The new instance can receive the site and settings needed for acceptance testing. It must remain closed to visitors and disconnected from the real transport. In the clone, replace To, Cc and Bcc recipients and remove production secrets from tested paths. Check deferred tasks and integrations using their own access. If a channel cannot be disabled on the account, postpone its test or disable the component in staging.

Use two fictitious inquiries. The first creates an expected notification in capture, with a reference readable end to end. The second corresponds to an earlier attempt the application believes unfinished. Keep this second entry pending verification. Capture must show the actual recipient, role, identifier and sending instance. A screen where the form displays the test address does not prove that the relay used that address.

Set cutover conditions before the trial. For example, require zero messages to the real system during acceptance testing, zero unknown inherited attempts automatically retried and only one expected notification for the reference inquiry after the role change in a test transport. Also check that an attempt from the old site is refused after the change. The result applies to the paths actually exercised. An additional plugin or email path requires a separate check.

Decide what happens to the queue and transfer sending authority

As cutover approaches, block new jobs on the old site or use an explicit procedure for holding inquiries. Inventory ongoing attempts and appoint someone to reconcile them. For each notification, identify the inquiry ID, expected recipient, last attempt and last known result. If the form uses Action Scheduler, its administration screen provides task statuses and logs. It is not, by itself, an SMTP delivery log.

For an ambiguous attempt, seek positive evidence from the relay or controlled receiver. Match the identifier, address and time. If the relay accepted the message, record this result and do not trigger a second transmission solely because the local log is incomplete. If actionable evidence shows that the relay did not accept the message, the operator can authorize a retry in the designated instance. Without sufficient evidence, keep the entry on hold and decide who handles the inquiry.

When transferring sending authority, first disable real processing on the old site and verify the block. Apply the destination’s transport configuration after checking the transferred log. A complete site replacement may carry over capture configuration or pending tasks. If the tool does not document selective settings transfer, recheck the destination after the operation. The ability to restore the old site version does not make an already transmitted email reversible.

Keep a register stating who closed each case and when. If returning to the old site, first close off sending from the destination, then reconcile attempts processed since the transfer. Reuse the same identifier for deferred notifications. A stable identifier helps reconciliation, but SMTP does not guarantee unique delivery based solely on that identifier.

• Record the last attempt and notification identifier before copying a queue.
• Record whether relay acceptance is confirmed, rejection is confirmed or the outcome remains unknown. Keep unknown cases on hold.
• After handover, check in dedicated capture that a task executed by the old site is refused and the new site’s reference inquiry produces the expected notification.

Replay acceptance without a visible acknowledgment

The attached exercise uses a form, a register and two in-memory transports. The capture transport represents acceptance testing. A second register represents a fictitious relay for the real system. An inherited notification has already passed through this relay before the role change, but the application lost its acknowledgment. The old site remains present in the simulation. No email service starts and no data leaves the computer.

The test first checks that the staging form records the inquiry and writes only to capture. An incorrect destination is blocked. At cutover, the simulation requires stopping the old sender before activating the new one. It then blocks retrying the inherited notification until relay evidence is consulted. After reconciliation, a new job produces only one trace despite a second processing request. Another case simulates an established rejection and its authorized retry.

The report must show ambiguous states, refusals and accepted entries. It explains why the form’s visible response is insufficient and why reverting configuration does not undo traces already emitted. This mockup validates neither SPF, DKIM nor delivery by a provider. On hosted staging, reproduce the checks with authorized destinations and retain evidence from the selected transport.

• Extract the ZIP into an empty folder and run node exercice.cjs with Node.js 22 or a compatible version.
• Compare the output with attendu.json. You should see one staging capture and one trace per accepted notification on the fictitious relay.
• On hosted staging, repeat checks separately using the chosen transport’s log. The ZIP’s register runs in a single process and does not prove simultaneous task shutdown on two servers.

Choose according to the access needed to sign off cutover

Choose TransIP Managed WordPress 20 GB if the team can perform all checks from WordPress, the panel and its email service. Staging is advertised and its replacement procedure documented. This choice assumes that the form exposes its log, the team can disable the clone’s real sending path and relay evidence is accessible without opening files or the database.

Choose Combell Business if the operator needs to inspect files or the database to diagnose the form migration. The setup guide states that these are accessible on managed WordPress. Confirm their scope on the clone and the support channel during the planned window. If the requirement concerns outbound network traffic, require a separate answer from the host or email provider. File access alone does not demonstrate that all notifications are blocked.

Postpone cutover if nobody can prove suspension of the old sender, the clone retains a real recipient or the register contains an ambiguous attempt that would be automatically retried. The copy can remain useful for checking the form while the account holder organizes transport handover. Once the conditions are met, retain the report and test references without secrets or people’s addresses.

Further reading

• Read the TransIP profile
• Read the Combell profile
• Compare WordPress email routing
• Download the notification checking mockup (ZIP)