I realise we can use .NET code to execute IOM.exe (effectively simulating executing it from the command-line), but what would be even better would be to provide a proper .NET-based API for executing an ImportOmatic import profile. This would provide a much stronger automation option than either scheduling IOM.exe or executing it as a separate process - the calling .NET code would control when / how / with what parameters the import was executed, and could receive notification of the results either as a return value from the invoked method, or via the standard .NET exception mechanism - much better than having to try to get .NET code to parse the results of the command line / contents of error / exception files. Additionally, you could even support passing in the records to be processed as a parameter rather than having to write them to file, even if it was just in a simple list of strings. I suspect much of this is already there in the IOM codebase, it would just need to be exposed and would make IOM even more attractive as an automated integration solution.