Before October 30: migrate Brevo bulk contact updates without losing fields

October 16, 2026

If an integration still uses Brevo's old bulk contact-update endpoint, inspect it before October 30. Moving to the import endpoint changes more than a URL: the operation is asynchronous and field-handling choices can change stored data. Record how you will recognize completion, preserve existing values and recover from an incorrect update before replacing a production job.

A May announcement with an October deadline

Brevo's May 12 announcement sets October 30, 2026 as the effective deprecation date for POST /contacts/batch and points to /v3/contacts/import. From this guide's October 10 review, that is 20 calendar days away. The notice says the old endpoint may stop working after deprecation; it does not establish a guaranteed shutdown at midnight or an exact outage time.Sources: Brevo — POST contacts batch deprecation

The import reference describes an asynchronous operation. A successful acceptance response returns HTTP 202 and a processId. That is evidence of an accepted request, not proof that all contact records have finished updating correctly. A migration needs a way to follow the process and reconcile the final data, not simply treat every accepted response as a completed job.Sources: Brevo — asynchronous contact import

Protect field meanings, not only record counts

The reference lists updateExistingContacts as true by default. Setting emptyContactsAttributes to true can clear existing values with empty fields. Map the meaning of missing, empty and intentionally cleared fields before sending data. A request with the right number of contacts can still produce the wrong result if its field policy does not match your CRM's intention.Sources: Brevo — asynchronous contact import

Imagine a hypothetical nightly job that updates a customer's city but does not have a phone number. An empty phone field may mean “unknown in this input,” not “erase the stored number.” Define that distinction and verify the selected parameters with synthetic data. This example does not report a Brevo import or establish the result of your particular request.

A migration checklist

  1. Search your current code, connectors and scheduled jobs read-only for the old endpoint. Record owner, frequency and the data it changes. No match in one repository does not rule out an external connector, and this article has not inspected your environment.
  2. Create a mapping for attributes, empty fields, repeated contacts and target lists. State which existing values must remain and which should be cleared. Design a small synthetic test set that can expose differences without importing real customer contacts.Sources: Brevo — asynchronous contact import
  3. Plan processId tracking and completion notification using the documented mechanisms available to your integration. Reconcile intended changes with the resulting records. Keep request acceptance, process completion and correct final values as three separate checkpoints.Sources: Brevo — asynchronous contact import
  4. Preserve the necessary backup and recovery procedure before an authorized migration. Record test outcomes and who may approve the production change. LessWork Lab did not import contacts, run the old or new endpoint or prove that a rollback works in a reader's system.

Migration does not by itself require an upgrade

The research found no requirement to buy a paid plan merely to replace this endpoint. Your existing subscription remains part of the cost, but its actual plan is unknown here. Official English help describes Free at $0 and optional Starter from $9 per month. These are public displays, not a country-specific quote or proof of every account's API entitlement.Sources: Brevo — pricing plans

Developer time, backups and connector maintenance were not priced. Country, currency code, taxes and required capacity were not locked. No negotiated reader code or verified promotional deadline was obtained. Prioritize data integrity rather than buying a plan because a technical deprecation is approaching; price a paid change only if your actual requirements justify it.

Two questions to answer before deployment

Does HTTP 202 mean the whole list is updated? No: the documented response indicates acceptance with a processId. Follow completion and inspect the resulting data. This guide does not invent a fixed processing time or claim that every accepted record succeeds.Sources: Brevo — asynchronous contact import

Will a blank input leave the old value unchanged? Do not assume that. The emptyContactsAttributes choice can clear existing values, and updateExistingContacts also needs review. Test the intended mapping with synthetic examples before using real records; no product test was performed here.Sources: Brevo — asynchronous contact import

Official notice and import documentation reviewed October 10, 2026. No exact shutdown time, tested migration, time saving or ROI is established. Brevo's public affiliate information describes approval and traffic requirements and prohibits PPC; a fixed CPA amount for this applicant is unknown. Account approval, a usable referral link, qualifying commission and Taiwan commercial payout remain unverified. This technical candidate contains no affiliate CTA.Sources: Brevo — affiliate eligibility · Brevo — referral and promotion restrictions

Official sources

Reviewed:

Related reading