Migration Overview
Migrating to Olympus can be done incrementally. Run both systems in parallel during transition to ensure data consistency.
Migrating to Olympus can be done incrementally. Run both systems in parallel during transition to ensure data consistency.
Map your existing API calls to equivalent Olympus endpoints. Most operations have direct equivalents with improved response formats.
class="text-white/class="text-amber-400">30 italic">// Middesk to JANUS mapping
class="text-pink-400">const endpointMap = {
class="text-white/class="text-amber-400">30 italic">// Middesk -> JANUS
class="text-emerald-class="text-amber-400">400">'POST /v1/businesses': class="text-emerald-class="text-amber-400">400">'POST /v1/entities/verify',
class="text-emerald-class="text-amber-400">400">'GET /v1/businesses/:id': class="text-emerald-class="text-amber-400">400">'GET /v1/entities/:id',
class="text-emerald-class="text-amber-400">400">'GET /v1/businesses/:id/documents': class="text-emerald-class="text-amber-400">400">'GET /v1/entities/:id/filings',
};
class="text-white/class="text-amber-400">30 italic">// Response transformation
class="text-pink-400">function transformResponse(olympusResponse) {
class="text-pink-400">return {
id: olympusResponse.entity_id,
name: olympusResponse.legal_name,
status: olympusResponse.status.toLowerCase(),
class="text-white/class="text-amber-400">30 italic">// ... map other fields
};
}Run both systems simultaneously, comparing results to validate data consistency before full cutover.
For cached or stored data, create migration scripts to update references and formats to Olympus conventions.
Create comprehensive test suites that validate functionality against your existing system before cutover.
Explore our API documentation to start building with Olympus.