Tidal to ActiveBatch Migration Expert

I need hands-on help moving a large portfolio of Tidal workload automation jobs into ActiveBatch. ActiveBatch support has confirmed that no automated converter exists for our current release, so every job, calendar, dependency chain, and notification rule must be rebuilt manually inside the new scheduler. What you will be working with • Hundreds of operational-data jobs, many with intricate upstream and downstream relationships. • A mixture of calendars, variables, file and database triggers, plus cross-environment hand-offs that currently live in Tidal. • A production environment that must remain fully secured during the migration; we will provide the specific security controls and change-management steps you need to follow. Key expectations • Analyse each Tidal job and map its logic, schedules, resources, and alerts to an equivalent ActiveBatch object. • Re-create complex dependency chains so that run order, retries, and failure handling behave exactly as before. • Validate every migrated job in a non-prod ActiveBatch instance, then promote to production under our security procedures. • Produce concise documentation of the migration steps and any gaps or design improvements you introduce. Acceptance criteria 1. All jobs execute successfully in ActiveBatch with the same timing, parameters, and outcomes seen in Tidal. 2. Dependency graphs are verified through end-to-end test runs. 3. Security checklist (account usage, credential stores, audit trails) is signed off by our infosec lead. 4. A migration report is delivered summarising mappings, changes, and outstanding items. If you have deep, recent experience with both Tidal and ActiveBatch and can demonstrate prior manual migrations, I’d like to hear how you would approach this project and your estimated timeline for each phase.

Project ID: 40152519