Can AI migrate COBOL on its own?+
**No, and we do not claim it.** LLMs significantly accelerate reading, mapping, and target-code generation on known patterns. But critical legacy migration requires senior architects who arbitrate ambiguities, validate structural choices, and sign the discrepancy registry. The ATLAS Legacy promise is **AI-assisted human predictability**, not blind automation.
How long does an ATLAS Legacy migration take?+
It varies with size and complexity. For a single-user Delphi application of 50,000 lines, plan **3 to 5 months** with a 4-5 person cell (1 architect, 2 target developers, 1 tester, 1 client business referent). For a multi-application COBOL mainframe program of 500,000 lines, plan **12 to 24 months** by functional slices. The Discovery phase typically lasts 4 to 8 weeks and conditions the rest of the budget.
How do you guarantee functional parity?+
Three levers. **Automated parity tests**: replay historical test sets on the target and measure equivalence rate before cutover (target > 99% on critical paths). **Signed discrepancy registry**: every gap is documented, arbitrated between Access and the client, and signed as a contractual deliverable — no post-cutover surprises. **Dual-run**: source and target run in parallel during hyper-care, with gap monitoring. Any unexpected gap triggers a framed rollback.
Do you operate directly or through a partner?+
Both configurations exist. **Direct**: Access International carries the relationship and delivery end-to-end, from Intake scoping through cutover and hyper-care. **Through partner** (most frequent): we operate as a nearshore assistance cell on behalf of an integrator ESN (Canadian or French) carrying the end-client relationship. The ATLAS methodology is packaged for co-deployment with practice sharing and training.
What are the client-side prerequisites?+
**Full source-code access** (programs, copybooks, JCL, DB schemas, deployment scripts). **Available business referent** a few hours per week to arbitrate ambiguities (critical legacy always has business rules undocumented in the code). **Access to historical test sets** or, failing that, capture of representative test cases at mission start. **Clear decision on target** (TypeScript, Java, .NET, Logic Apps) — we support that decision if not yet made.