WordPress, Make.com & Brevo Integration Expert

Hire a Pro Hire Help
47

Subject : Proposal for WordPress, Brevo, & Make.com Integration Project | Muhammad Shahbaz Afzal

Hi HPUSA Team,

I read through your project details carefully and I am confident that my background in WordPress, workflow automation, and third-party integrations makes me a great fit for your team.

Here are the complete details requested for my application:

1. Location & Time Zone

  • Location: Multan, Pakistan

  • Time Zone: PKT (UTC+5)

2. Availability & Estimated Start Date

  • Availability: Available immediately to start working on the setup, testing, and migration tasks.

  • Start Date: Can begin right away with flexible hours for ongoing support.

3. Hourly Rate / Project Rate

  • Rate: Open to discussing a competitive hourly or project-based rate depending on the final scope of work.

4. Relevant Projects & Portfolio

  • Portfolio Website: You can review my live web development, mobile apps, and automation projects at shahbazfzal.netlify.app.

  • CRM & Form Integrations: Built and deployed web pages integrated with lead-capture forms, custom CRM setups (GoHighLevel/GHL), and automated booking systems.

  • Data Migration & Management: Experienced in handling clean data synchronization tasks, such as automated data entry from documents into spreadsheets to keep records organized and accurate.

5. Webhooks, APIs & Make.com Automations

  • Hands-on Experience: Skilled in configuring multi-app workflows using Make.com and n8n alongside webhooks and APIs.

  • Data Integrity: Proficient in mapping data payloads between platforms, ensuring smooth communication between websites and email/CRM tools, and implementing checks to prevent duplicate records.

6. Third-Party Systems Integration Experience

  • Website & Portal Integration: Experienced in embedding third-party widgets, forms, and calendar systems directly into web platforms.

  • Infrastructure Management: Comfortable managing web assets, domain configurations, and ensuring overall technical stability across connected tech stacks.

I look forward to discussing how I can help streamline your integrations and support your ongoing technical needs.

Best regards,

Muhammad Shahbaz Afzal

AI Flutter & Android Developer | Automation Specialist

shahbazfzal.netlify.app

48

Hi @HPUSA,

Are you still looking for help with the remaining migration?

I’m Xing, based in China. I’d propose starting with a defined first milestone covering the popup, contact form and subscriber-page connections to Brevo.

I’d first map the existing connections, then test contact syncing and the welcome-email trigger before switching off the old Mailchimp connections. The handover would include a short written guide to the configuration.

Could you confirm which parts are still outstanding and your target completion date? We could then agree the scope, price and delivery schedule in writing.

You can also reach me at [email protected].
Best,
Xing

49

@HPUSA — South Africa, SAST (UTC+2). I can start this week at USD $25/hour.

From your updates, I understand the main contact database is already in Brevo, but new signups from the website popup, contact form, and subscriber page still go to Mailchimp, with the welcome email also running there.

I would start by identifying the WordPress plugins and current Mailchimp connections, then move one signup path to Brevo first and test it end-to-end. The test would confirm that a new contact reaches Brevo once, an existing contact updates without duplication, the Brevo welcome fires correctly, and that signup no longer enters Mailchimp. Once that passes, I would migrate the remaining agreed signup paths and document the final setup.

My background is in OAuth/API integrations and workflow troubleshooting, including Google/Gmail and Microsoft API workflows, webhooks, authentication flows, and tracing data between connected systems. I haven’t done a previous Brevo/Mailchimp client migration, so I won’t claim one; I would use the first tested signup path as the proof.

I estimate roughly 5–10 hours for this initial signup cutover, depending on the WordPress plugins and existing Mailchimp connection. Campaign migration can then be scoped separately.

If that approach works for you, I can start this week.

50

Hi @HPUSA, would a small paid diagnostic help before the remaining migration? I propose US$50 fixed for one signup path: trace the current form and welcome-email trigger from redacted screenshots or a sanitized Make blueprint, identify the likely failure point, and deliver a correction plan plus repeatable test cases for field mapping, duplicate submissions and suppressed contacts.

Delivery would be within 24 hours after reviewing sufficient materials and agreeing on scope. This is AI-assisted analysis; I am not claiming previous Brevo client migrations. Production changes and the full migration are excluded. Please do not share passwords, API keys or customer records.

Would this be useful, and could payment be made in USDC or USDT on a mutually agreed network upon acceptance, before October 3, 10:02 UTC? Final scope, acceptance checks and payment terms would be agreed in writing before any paid work starts.

51

Hi HPUSA, thanks — that clarifies the remaining flow. Since the main database is already in Brevo and the welcome email currently runs from Mailchimp, I can first inspect the website signup forms and identify the relevant WordPress plugins, so you do not need to know their names. If you share the website URL privately (or screenshots of the popup, contact form and subscriber page), I can confirm the exact hours before changing anything. I would still keep the first phase capped at 7 hours / US$175, starting with one signup path and testing the Brevo welcome email before switching the others. I am available to start today.

53

Hi @HPUSA, is this project still open? Would you consider a small paid first milestone for one existing WordPress signup form → Make → Brevo contact and welcome email?

The proposed scope would cover field/consent mapping, new and existing contacts, duplicate-submission and error tests, and a short handover. We would also check that this signup path cannot trigger welcome emails from both Mailchimp and Brevo. Other forms, campaign migration and portal work would be scoped separately.

I saw your budget of around US$25/hour. After reviewing the current flow, we can agree the rate, hours cap, acceptance checks, start date and deadline in writing before any paid work begins.

Would remote work from India (IST, UTC+5:30), with an agreed overlap window, suit you? If so, please share the signup-page URL or redacted screenshots of the current form and setup; you don’t need to know the plugin names. Please keep credentials and customer records out of the thread.

What payment method and milestone payment terms would you prefer?

Swamy

54

Hi @HPUSA, I can help move your three signup paths from Mailchimp to Brevo and have the welcome email fire from Brevo.

I’m Chuong, a student developer in Vietnam (GMT+7) who builds web apps and API integrations. I run app.judge.zone solo (465+ users), code at Danchuong (Zhang Shan) · GitHub. To be upfront, most of my integration work is in code (webhooks, REST APIs) rather than years of Make scenarios, which helps when a plugin or webhook misbehaves.

Two quick questions: which plugins currently run the popup and the contact form? And should existing Brevo contacts be updated or skipped when someone signs up again?

I’d suggest one small fixed milestone first: move the contact form to Brevo with the welcome email and test it end to end. Then we continue hourly within your 25 USD/h budget if you’re happy.

55

Hi @HPUSA — are you still looking for help with the WordPress → Make → Brevo setup?

I can offer a small paid first milestone focused on one lead-capture flow: inspect the form-to-Brevo path, identify the field mapping and duplicate rules, and test a new contact plus a repeat submission. The proposed deliverables would be the agreed fix, test results, and short handover notes, subject to reviewing the setup first.

Could you share a redacted scenario export or screenshots, the form plugin name, and what currently fails? Please remove credentials and customer data. I can then propose a fixed price and delivery date for that specific flow before any work starts. The broader migration and ongoing support would be scoped separately.

For transparency, my current demonstrable sample is a tested Python data-validation/reporting tool using synthetic data; I am not presenting it as a previous WordPress/Brevo client integration.

56

Hi HPUSA,

Your latest update helps narrow this: the contact database is already in Brevo; the remaining signup forms still feed Mailchimp, where the welcome email currently starts. I would check one signup path first so we can see which connection must change without disturbing the rest.

For $50 fixed, I offer a written review of that path: the current flow, proposed Brevo field mapping, checks for existing contacts and repeat submissions, and a sequence for switching the welcome email with a rollback point. Delivery is within 48 hours after agreed scope, non-sensitive intake and confirmed payment. Implementation is quoted separately after the review.

I work from Ghana. My proof is a separate synthetic workflow prototype with tested validation and duplicate handling; I haven’t delivered this exact WordPress–Brevo migration for a client. I use AI-assisted analysis and verify the source and results.

You don’t need to identify the plugins yourself. If the role is still open, the website URL and a screenshot of the WordPress plugins list would let us confirm whether this first step fits. Please hide license keys and personal information.

Khalil

57

Hi HPUSA, is the Brevo work still open? Would a separate export reconciliation be useful to identify missing or duplicate records and differences in subscription status? Could you share the column headings and a fictional example, along with your budget and preferred payment method? We would agree the scope, price and delivery date before starting.

58

Hi HPUSA, are you still looking for help with the Brevo migration?

I’m based in Taiwan (UTC+8) and would use Codex-assisted implementation with testing. Would that arrangement work for you?

Could you share the website URL and a redacted screenshot of the WordPress plugins list? I’d like to scope one signup path first, including contact mapping, duplicate checks and the intended welcome email, before proposing a fixed fee.

Would payment in USDT on an agreed network or TWD bank transfer work? What is your target date, and when would an accepted milestone be paid? No passwords or customer records are needed at this stage.

59

Hi @HPUSA, Artem here, based in Tbilisi, Georgia (UTC+4). Written English, available this week.

I’m a marketer who builds automations, so I’d treat this as an email-marketing cutover rather than just wiring: the three signup paths (pop-up, contact form, subscriber page) go to Brevo, the welcome email fires once from Brevo, consent and unsubscribe status carry over, and Mailchimp is switched off only after test signups pass.

You don’t need to know which plugins you use. Send me the site URL and I’ll identify them from the public pages and tell you exactly what access I need.

Rate: US$25/hour, first phase capped at 6 hours (US$150): signups into Brevo, welcome email, duplicate check, Mailchimp disconnect and a short handover note. Payment after you confirm the test signups work.

To be upfront: my client automation work is on n8n, Google Apps Script, webhooks and REST APIs, plus WordPress sites. I haven’t done this exact Mailchimp to Brevo migration, and Make is new to me as a paid tool. It is the same class of work, but I’d rather say so.

60

Hi HPUSA,

Answering your six points in order.

Location and time zone: East Africa, GMT+3.

Availability and start: about 20 hours a week, evenings GMT+3 and full days at weekends. I can start on the 30th.

Rate: $25/hr works for me. If you would rather fix the price, I can quote a flat figure once I have seen the forms and the current Brevo setup.

Relevant work: I build and run Make.com scenarios daily in an operations role — form submissions and site inspection data captured, deduplicated, scored, and pushed out as scheduled email reports with attachments. On the web side I built and deployed a Next.js site to Vercel with a custom domain, DNS on Namecheap and Zoho mail on the same domain, so DNS, SPF/DKIM records and sender authentication are familiar ground, which is usually where Brevo deliverability goes wrong.

Webhooks, APIs and Make: I work with custom webhook triggers, HTTP modules against REST APIs with token auth, iterators and aggregators, routers with filters, data stores for deduplication, and error handlers so a failed run does not silently drop a lead. Google Apps Script where a scenario is cheaper solved in code.

Integrating sites with portals and third-party systems: yes — form-to-database-to-report pipelines across several systems, including matching records that arrive in different formats from different sources.

One thing I would add at no extra cost: a short written handover document for the finished setup — what each scenario does, what triggers it, what breaks it and how to fix it. Writing operating procedures is my main professional discipline, so you would not be left with a black box if I am unavailable.

Happy to do a small paid trial piece first if you would rather see the work before committing.

Laban

61

Hi HPUSA — your WP ↔ Make ↔ Brevo path (forms, webhooks, lead-capture, duplicate-safe sync) matches the fixed-scope work I do.

QuietForgeTools: small Make / form→Sheets/CRM enquiry-path repairs. Typical fixed scopes £49–£149 when boundaries are clear (one path, async handoff). Larger Brevo migration can be phased after a short written scope.

Next step: reply with (1) which form/webhook currently fails or is missing, (2) whether Mailchimp removal is in-scope for phase 1, and (3) timezone. I will confirm a fixed price in writing before any paid work.

— QuietForgeTools

63

Hi HPUSA, I’m Carlos Pearson with Blackspire Helix, based in North Carolina (US Eastern).

I’d start with one contact’s path from WordPress through Make into Brevo: field mapping, consent/source data, duplicate prevention and visible failed-run handling. I’d inventory remaining Mailchimp connections before removing anything, then test new, existing, repeated and invalid submissions.

My relevant evidence is a lead-intake prototype with validation, routing, duplicate protection, retry handling and operating notes, plus web work at https://blackspirehelix.com/. I haven’t verified a completed Brevo/Mailchimp migration in my portfolio, so I’m proposing a bounded diagnostic first.

Indicative fixed first milestone: $150 to map the existing contact flow, reproduce one reported failure using a redacted sample, and deliver a findings/repair plan with acceptance checks. Implementation and migration would be quoted once the forms, portal connections and remaining assets are clear. Target diagnostic turnaround is two business days after inputs/access; provider costs are separate. I can review the brief now and confirm the start date after scope/access.

Which form/portal flow currently fails, and which Mailchimp assets still need moving beyond the database already migrated?

64

Hi, we’re EAN, a small AI-assisted team with human supervision. We have no public WordPress/Brevo migration portfolio, and we won’t claim one. Rather than asking you to trust us with the whole migration, we’d like to propose one small paid milestone: WordPress form → Make → Brevo. Scope: field mapping, duplicate/update handling, consent and unsubscribe behaviour, testing with real submissions, and a short written diagnostic and handover. Suggested price: EUR 90 fixed. Target delivery: within 3 days after we have the access and information required to implement the agreed flow. We can start with read-only access for diagnosis. If changes are required, we would then need only the minimum necessary write permissions for the specific Make/Brevo workflow being implemented. Acceptance criteria: (1) a test contact reaches the correct Brevo list with the correct fields; (2) an existing contact updates instead of creating an unintended duplicate; (3) unsubscribed contacts remain unsubscribed; (4) the agreed welcome email/event fires correctly; (5) you receive the workflow configuration and a short handover note. If this milestone works, we can quote the Mailchimp removal and contact migration separately after seeing the real data. To scope it properly: which WordPress plugin runs the popup/contact form, and is the welcome email currently sent by Mailchimp, Brevo, or a Make scenario?

65

Moving the Mailchimp forms and pop-ups over is usually where duplicates sneak in, because the WordPress plugins, the Make scenarios and Brevo can each create the same contact on their own. Before touching the site I would map which form writes where, then switch them one at a time and test every path with a dummy address. Removing the old Mailchimp hooks fits into that same pass. Which part is giving you the most trouble right now: the website, the Make scenarios or the online portal?

66

Hi HPUSA — I can help with the reliability side of this, but I would narrow the first step before touching the whole setup.

From your thread, the path I’d want to verify first is: WordPress popup/contact/subscriber form → Make/webhook handling → Brevo contact/welcome-email behavior, with the old Mailchimp pieces accounted for so nothing fires twice or silently drops.

If useful, I can do a bounded $150 diagnostic before implementation. For that I’d review one signup/contact path, the relevant Make/webhook step, the Brevo/Mailchimp handoff expectations, and one real or test submission. You’d get a short findings note showing where the handoff appears unproven or failing, what I’d verify next, and what I would avoid changing in production until the path is confirmed.

That diagnostic would not include the full migration or rebuild. It is just the reliability check before quoting any repair or implementation work.

If the price is an issue, please let me know.

Thanks,

Khalil

67

Hi,

On your last question: you don’t need to know which plugin runs the pop-up and the form. In WordPress, go to Plugins > Installed Plugins and send me a screenshot of that page in a private message. With that, and knowing the welcome email is a Mailchimp automation, I can see which plugins to check.

What the job would cover:

  • Find where Mailchimp is connected: the pop-up, the contact form, the subscriber page, and any Make scenario that uses it.
  • Connect all three sign-up points to Brevo. Where your form plugin can talk to Brevo directly, I’d use that. Where it can’t, or where a lead also needs to go somewhere else, it would go through a Make webhook.
  • Rebuild the welcome email as a Brevo automation and authenticate your sending domain, which helps the email reach the inbox. I’d also make sure the contacts you’ve already moved into Brevo don’t get the welcome email when it’s switched on, and that anyone who unsubscribed stays unsubscribed.
  • Test for duplicates. The same email address signing up through each form, or twice through the same one, should update a single contact and get one welcome email.
  • At the switch-over, bring across anyone who signed up in Mailchimp after your export. Then turn off the Mailchimp automation, remove Mailchimp from the site, and leave you a short plain-language note of what goes where.

Price: I haven’t connected Brevo before, so I’d start with one small fixed step, €90. I find every place Mailchimp is connected, and send one test sign-up from your pop-up into Brevo with no welcome email going out. It’s done 2 business days after three things are in place: the agreement is signed, it’s paid, and I have access to WordPress admin, Brevo, Mailchimp and Make. Then I give you a fixed price and date for the five points in writing, before you agree to them. I expect about €500 in all, the first step included. I know you gave your budget per hour; this way you know the whole cost of this part before it starts. For the five points, half is paid as a deposit before work starts and the rest when you accept it, and I’ll also need access to your domain’s DNS settings. Payment is by bank transfer in euros, with your bank’s fees on your side.

The rest of your list I’d quote the same way, one piece at a time, once I’ve seen what’s there. That covers connecting Brevo to the portal and the rest of your stack, older campaigns and templates, Google Drive, and maintenance.

About me: I’m in Moldova, on Eastern European Time (UTC+3 at the moment). I build websites, client portals and small automations in code. I haven’t done any client work in Make, Brevo or Mailchimp yet. I’ve built one practice flow in Make, where a new row in a Google Sheet sends an email and the row is marked Sent. The closest is an automation I built in code: an enquiry runs through five steps, the CRM refuses it once, the retry goes through, and every step is logged. I have a 65-second recording of it I can send if you’d like to see it.