I have used Contact Form 7 for as long as I can remember. It is simple, it is reliable, and it rarely gets in the way. For most WordPress sites, that is exactly what you want.
When Flamingo came along, it felt like the obvious companion plugin. Same developer, same ecosystem, and a clear promise. A place inside WordPress where you can see every enquiry that has come through your forms.
Clients like that idea. They like knowing there is a backup. They like having a central place to check messages without relying on email alone. It is also a lifesaver when SMTP is broken or flaky, which does happen from time to time.
So for years, our stack has looked like this:
- Contact Form 7 to capture enquiries
- Flamingo to keep a record in the WordPress admin
- WP SMTP to deliver the email copy
That setup is solid, but if you have used Flamingo seriously, you will know it has a few rough edges.
Flamingo is useful, but it has quirks
The first one is small, but it never stopped annoying me. The name.
Trying to explain to a client that their enquiries are stored in something called “Flamingo” always felt a bit strange. Not a major issue, just an odd friction point when you are trying to keep things professional and clear.
The next one is more practical. The Address Book screen.
We have never used it. It feels like a tiny nod towards CRM functionality, but in practice it is just another place for clients and team members to get lost. The problem is that it is the first thing you see when you click into Flamingo, when what they really want is to see their actual enquiries. Instead they see a list of senders and wonder what you are looking at.
The inbox which is really just a list view of submissions has its own problems.
By default, Flamingo just gives you the basics in the table. Subject, sender, date. The trouble is that we never use a “subject” in our contact forms. It is usually just a hardcoded label based on the form or the site. So the only real way for spotting spam from this list is the email address which is often useful but will easily create false positives.
You end up clicking into submissions one by one just to answer basic questions like:
- Is this real or spam?
- What did they enquire about?
- Is this urgent?
When you are managing multiple client sites, those little frictions add up.
The real pain starts during development and staging
The issues became obvious once we started using Flamingo on sites that were under active development.
We host on Cloudways, and one of the reasons we like it is how easy it is to spin up a staging site. It makes development safer. You can apply updates, test changes, let the client preview everything, and then push to live.
The problem is what happens to Flamingo data while you are doing that work.
Enquiries do not stop just because you are working on a staging copy. Messages continue to come into the live site. Meanwhile, the staging site has its own snapshot of the database from the day you created it.
When you are ready to go live, the practical approach is usually to migrate the updated site and database changes back into production. But if you move a full database dump, you risk overwriting the latest Flamingo messages that came into live while you were building and testing.
So you end up with two bad options:
- Export and import the entire database and accept that you will lose submissions in WordPress.
- Create an off line spreadsheet of submission so that there is some central back up.
WordPress and Flamingo do not make this easy.
Flamingo can export messages to a spreadsheet, which is helpful for reporting, but there is no import function. So the one thing you actually need during a migration is the one thing Flamingo does not provide.
WordPress does have its own import and export tools, and technically you can move Flamingo posts that way. In reality, it is incredibly limiting, you have the option to export everything and that is it. In our experience it either times out, runs out of memory to it is in all actuality useless. It is not designed for the very practical real world situation where you only want to move some data without touching the rest.
That was the moment I realised we needed a dedicated tool for this.
Attachments confused clients as well
One more thing kept coming up.
Flamingo does not store attachments. It stores a hash reference, which is not useful to a client who just wants to see what someone uploaded.
From a technical point of view, I understand it. Storing uploads inside a message database is not trivial. But from the client’s point of view it is confusing. They are looking at an enquiry in the admin area and they see something that looks like it should contain a file, but it does not.
That confusion generates support questions, and it creates a trust problem where the client assumes the enquiry has not been captured properly.
What AC Advanced Flamingo Settings does
AC Advanced Flamingo Settings exists to smooth over those exact friction points. It is not trying to replace Flamingo, and it is not trying to turn Contact Form 7 into a CRM. It is just focused on the stuff that makes day to day usage less painful.
Here is what it does in plain English.
1. It lets you export and import Flamingo messages properly
The main feature is a proper export and import workflow designed for real migrations.
You export the messages from the site that has them.
You import them into the site that needs them.
This makes staging and pushing changes live much less stressful, because you can move the enquiries without having to move the entire database.
It also solves the classic “new host migration” issue where you want a clean move but you do not want to recopy everything, especially if the site has had a lot of activity in the meantime.
2. It makes it easier to manage the admin experience
If you have ever had a client click into Flamingo and get confused by the Address Book first, you will know why this matters.
The plugin includes settings that let you tailor the Flamingo admin experience so it matches what clients actually need. Less confusion, fewer emails asking “where did the enquiries go”.
3. It helps with the common frustrations
It is built around the problems I kept seeing repeatedly:
- Needing to move enquiries between environments
- Clients wanting a simple place to check enquiries
- Clients being confused by the default admin layout
- Time wasted clicking through entries just to spot spam or locate real messages
It is not a huge, complicated plugin. It is intentionally focused.
Who this is for
If any of these sound familiar, you are probably the target audience:
- You use Contact Form 7 and Flamingo on client sites.
- You create staging sites and do regular development work.
- You have ever worried about losing enquiries during a migration.
- You have had clients complain they cannot find their messages.
- You want a simple export/import tool that does not involve database dumps.
How to try it
Install it from the WordPress plugin repository by searching for:
AC Advanced Flamingo Settings
Once it is active, you will find the settings inside the Flamingo area in your WordPress admin.
If you are moving a site right now, start with the export/import feature. That is the one that removes the biggest headache.
A quick favour if it saves you time
This plugin exists because I needed it in my own workflow. If it saves you a migration headache or prevents you losing enquiries during staging work, a review on WordPress.org helps more than you’d think. It is the difference between a plugin quietly sitting there, and it actually reaching the people who need it.
If you want, reply with any Flamingo pain points you have run into. If enough people have the same problem, we might include it in our roadmap.
Comments
Submit a Comment