If you are still submitting MigrationWiz jobs manually in the portal UI for every project, it is worth asking whether your project volume has reached the point where API automation makes more sense.

BitTitan offers a REST API for MigrationWiz that lets you create projects programmatically, manage user lists, submit jobs, and pull status data. For one migration project with 300 accounts, the portal UI is typically the best fit. For a consulting practice or an internal IT program running 10 or more migration projects at the same time, the API is often what turns that volume into something you can run operationally.

In practice, the endpoints that tend to deliver the most value are: creating user lists via API upload instead of bulk CSV uploads through the portal; submitting jobs to trigger coordinated pre-stage passes across multiple projects; and retrieving status so you can drive a consolidated dashboard that shows progress across every active project at once.

Authentication is done using your BitTitan account credentials, and the API returns JSON responses. BitTitan also maintains documentation covering supported endpoints and request formats.

As a rule of thumb, the development effort starts to pay off once you have roughly three or more active migration projects running simultaneously. If you are below that, the portal UI usually handles the workload with less overhead than building and maintaining an API integration.

Are you using the BitTitan MigrationWiz REST API, or is the portal UI sufficient for your current project concurrency?

#BitTitan #MigrationWiz