As far as I can tell, the DocuWare message bus admin program deletes the queues, and they are rebuilt when the service is restarted. I'm not sure how one would select a different adapter via Powershell, or if it would matter (see KBA-35787).
It appears you concentrated on exporting everything first and saving the data in a DB (FoxPro), then imported it all using that DB and creating any needed cabinets or fields on the fly. That's pretty slick. I don't think I'm going to want to do that 'create' step, but I'll definitely look into coding an import processor. It looks pretty straightforward to me. Might have time to try an exporter, also.
Thansk, Mr. Kaufman. This may save us quite a bit of time.
I'm already using the old-fashioned multi-threading. Lots of experience with that...
If you wrote code to import multiple doc types simultaneously, then you went all-out. Did it report how many files were imported? For us, single doc types per run are fine. I would like to see a snippet or two, if possible. The code examples look fairly straightforward. Is that the case?
Joe Kaufman: You note in your response 3 years ago that importing with import jobs was really slow in testing, so you wrote an app to do so. How much faster is that approach? I've got tons of data to move from Fortis.