You would have thought I’d have figured out the publishing mechanism for this newsletter, but guess not given the missing subject for yesterday’s note.

While this newsletter is a tad wonky from an implementation standpoint, it does highlight another question that should go on the checklist for investigation: what automations are in place, which will need to be stopped, and which will need to be continued by the acquired company?

May seem straightforward and something else left for the integration of specific custom apps, but there are plenty of cases where we have jobs that run periodically:

  • Batch jobs running payroll every couple of weeks
  • Nightly billing runs
  • Daily sales and financials
  • Security reports for new users added, removed, and updated permissions
  • A certain daily newsletter

You can see some of these being specific to a program, but most usually apply to a specific business goal. Some can be as frequent as within a few seconds, others as infrequent as once every 5 years. Some are included with your common SaaS packages, and others rely on a third-party orchestration framework (think Dell Boomi or Zapier).

Due to the periodic nature of these tasks, until you miss the first run or two and wonder why your KPIs are off, will you realize they were even there.

It isn’t just the programs that get migrated, but the business processes.

cab