Some loyal Spotler MailPro clients still have a few legacy filters in their license. Legacy filters have been read-only since 2015, but could still be used until now. With release 11.18, planned for the end of September 2026, MailPro will stop using legacy filter definitions.
Important: if a legacy filter is still used in a mailing, flow, trigger or another configuration, migrate it to the current filter editor before the release.
What is changing?
- Current filters: continue to work without changes.
- Mixed filters: filters containing both a legacy and a current definition continue to work with the current definition. No action is required.
- Filters with only a legacy definition: keep their name, but will be displayed without conditions after release 11.18 and will no longer be executed as a legacy filter.
The legacy filter data will remain stored in the background temporarily after release 11.18. It will be permanently removed in the subsequent release.
How to recognise a legacy filter
Go to Data > Filters and open the filter by clicking Edit.
A legacy filter has the "WHERE-part" filled, and the "Conditions" empty. The editor typically still has the orange WebPower colours.
If you only see the old, read-only filter definition and the current editor contains no Conditions, the filter must be updated.
If the correct Conditions are already shown in the current editor, a current definition has been saved and no migration is required.
Update a legacy filter
- Go to Data > Filters.
- Find the filter and click Edit.
- Check the conditions shown in the current filter editor.
- If conditions are missing, rebuild the old selection visible in the orange interface through the new interface with the correct database fields, operators and values.
- Click Test conditions and check that the number of matching contacts is what you expect.
- Click OK to save the filter in the current format.
Important: Always check the conditions and test result before using the filter.
What happens if you take no action?
A filter containing only a legacy definition will keep its name after release 11.18, but will be displayed without conditions. The legacy definition will no longer be used. As a result, a mailing, flow or trigger can no longer rely on the original selection.
More information
Contact Customer Support if you need help migrating or checking a legacy filter.