Microservices architecture for Data Ingestion Pipeline in .NET

I would like to get opinion/best practices on designing a brand new Data Ingestion Pipeline.

Key highlights of the new project are as follows:

• Download and Update data to/from SharePoint using Sharepoint APIs
• Download and Update data to/from JIRA/incident management application using JIRA APIs
• Download and Update data to/from SQL sources using provided APIs
• Download and Update data to/from external custom applications using APIs

I am considering the microservices architecture for the above project where I will be looking at creating 4 separate services for each of the above purpose.

And finally, a batch processing client that would execute all these API services using C# .NET

But I have been wondering if implementing microservices architecture will be overkill, and rather all I really need is a single client calling all these APIs directly without having to create above individual services.

I am happy to hear your opinion and ideas and can share more information if needed. Thank you in advance.