• State Not Answered
  • Replies 2 replies
  • Subscribers 263 subscribers
  • Views 81 views
  • Users 0 members are here
Options
Related

Wordfly Users - Next Steps

Jean Leonard
$organization

Hello! I'm wondering if any Wordfly users who have decided to stay with WF can share the steps they've taken since the data breach. Have you simply moved back to business as usual? Or did you do anything with your data or processes (or something else) before using the system again? Have you engaged any IT experts on your end? 

We have temporarily moved to MailChimp, and I do think we'll move back to WF soon... just wondering if there's something I need to do first. Our leadership is a bit hesitant to just hop back in! 

  • 0 $organization
    We moved back to WF as of this week, although we’re seriously looking at Prospect2 in the future for mostly unrelated reasons – it seems to open up greater automation possibilities without requiring as much backend DB coding to make them happen.
     
    We briefly looked at the idea of sticking with Mailchimp, and did a demo with the Monkeywrench folks to see if that might be an integration solution. But ultimately it didn’t provide deep enough integration, and would have required a lot of customization and rework to do what we were already doing with Wordfly. And we felt that doing a migration to Prospect2 would take more bandwidth than we had right now given other projects in the pipeline. So we decided to stick with the devil we knew for the moment.
     
    We did carefully audit the output sets we were sending to WF to make sure we were sending the minimum amount of data needed, and we also went through a process of making sure that any unsubscribes from MailChimp interlude were properly migrated back into Wordfly.
     
    During the outage we did connect with someone from the company that provides our cybersecurity insurance to make sure they were in the loop, and we discussed the pros and cons of various options. This was somewhat helpful in terms of providing some additional framework on how to think about the situation. (One takeaway was that these sorts of breaches are something of a fact of life these days, and we all do business daily with companies that have suffered some sort of data breach. So while obviously we want to take stringent steps to minimize risk, the mere fact that there was a breach may not be evidence of negligence or a litmus test reason to terminate a business relationship that is otherwise beneficial.)
     
    -David Dwiggins
    CIO
    Historic New England
     
  • 0 $organization

    Like we have resumed use of Wordfly. We plan to continue using it at least for the foreseeable future. Prior to Wordfly, we had been using MailChimp under the assumption that when we launched with Tessitura, we coudl implement the Monkeywrench API. When I had a demo about Monkeywrench, it became very apparent very quickly that the existing API is really not user friendly and to David's point, would require a knowledgable developer on staff to make it work at all. I also agree with David that data/security breaches happen to the best of the best so I am not sure that the grass is greener on that front elsewhere. 

    We have started to more regularly backup our non-Tessitura subscribers as that was one area that we found to be a gap in our process when the outage happened. 

    - Tracy Schneider

    Virginia Museum of HIstory & Culture