As there are many specific tools for data integration (Boomi, SSIS, informatica), you we think you should choose PowerShell.  Whether your data source is an Excel spreadsheet, a text file, a Rest APIs, or a software specific reporting tool, PowerShell should be the glue that binds them all together.  There are two reasons we think you should choose this direction.

First, if you run Windows, you have PowerShell.  Yes, we’ll almost certainly have to install some new modules.  But you have it.  And there’s no easier investment than no investment.

Second, you can find people to support and maintain what we build together. Which means you won’t become dependent on us.  We certainly hope that you become a long-term client.  But we don’t believe in consultant dependency syndrome. You should work with us because you want to, not because you’re afraid of firing us.

Third, there are lots and lots of resources available to learn about PowerShell.  With their MVP program, Microsoft has done a wonderful job encouraging expert content creation.   Blogs, videos, and conferences provide multiple ways to learn about PowerShell. And of course, we’re happy to train.

That said, we know that PowerShell is not THE answer to every data integration question. We’ll discuss some objections in our next post.

Adam Jacobson

Adam focuses on making enterprise software work for my clients. He’s consulted on financials, procurement and HR/Payroll. Currently, he and his small team focus on UKG Pro, especially Workforce Management (WFM). For more, check out his profile on LinkedIn https://www.linkedin.com/in/ajredthree/

Share

Leave a comment

Get tips and insights delivered to your inbox

Start a conversation with us

Call: 917-848-7284
Email: inquiries@redthree.com

Request a Consult