Migration center
Upgrade with evidence, not resemblance
Nine source-traced cutover plans cover every legacy and deprecated public guide in the repository snapshot. Each separates known lineage, candidate evidence, account-specific decisions, parity proof, rollback, and safe retirement.
The upgrade contract
Repository names suggest. Production evidence decides.
A candidate guide is a discovery lead—not an entitlement, compatibility promise, or automatic replacement. Every migration resolves the exact account, region, package or endpoint, authentication generation, quotas, lifecycle, and rollback before production traffic moves.
- 01Preserve behavior
Freeze the current journey and measurable contract before changing dependencies.
- 02Own the seam
Keep provider symbols, payloads, failures, and lifecycle behind application-owned adapters.
- 03Prove the journey
Compare reads safely; never shadow state-changing commands without product authority.
- 04Retire last
Keep rollback viable until cohort evidence and reconciliation are complete.
Source-derived inventory
Find your current integration
13 migration tracks
From2 source lines
EvidenceDirect Lineage
Core REST: MapmyIndia generation to Mappls contracts
Move trusted-server integrations across host, path, authentication, schema, and quota generations with contract evidence instead of string replacement.
From6 source lines
EvidenceAdjacent Evidence
Web maps and plugins: legacy scripts to a governed browser boundary
Replace global-script assumptions with explicit origin restrictions, lifecycle ownership, typed adapters, accessible fallbacks, and measured rendering parity.
From1 source line
EvidenceDirect Lineage
InTouch Android SDK lineage
Migrate tracking journeys as consent-aware state machines, preserving session identity, offline queues, background policy, and event ordering across SDK lines.
From1 source line
EvidenceDirect Lineage
InTouch React Native bridge lineage
Align JavaScript, wrapper, and both native dependency graphs while keeping tracking identity and recovery above the bridge.
From1 source line
EvidenceDirect Lineage
InTouch iOS SDK lineage
Move the explicitly deprecated MapmyIndia iOS tracking line to a release-qualified Mappls SDK while preserving durable session identity, consent, background execution, event order, and unknown-outcome recovery.
From1 source line
EvidenceSelection Required
InTouch REST contract generation
Re-contract a stateful telematics integration without confusing a newer repository name with a confirmed endpoint or write-compatible product generation.
From2 source lines
EvidenceSelection Required
Cordova and Ionic: stabilize, then migrate by journey
Turn an aging hybrid integration into replaceable application capabilities, then move complete journeys to a confirmed web, native, or cross-platform target.
From2 source lines
EvidenceDirect Lineage
React Native maps and REST wrappers
Move beta-era bridges to a release-specific Mappls wrapper while testing the Android and iOS implementations as separate products.
From1 source line
EvidenceDirect Lineage
Flutter map plugin lineage
Replace the explicitly obsolete MapmyIndia Flutter plugin with a release-qualified Mappls line while treating Dart, Android, iOS, and native SDK versions as one reproducible compatibility graph.
From1 source line
EvidenceDirect Lineage
Android vector map SDK lineage
Move the explicitly deprecated MapmyIndia vector SDK line to an approved Mappls Android release through a narrow application map boundary and a clean device/release qualification matrix.
From1 source line
EvidenceDirect Lineage
iOS map and API package lineage
Resolve modular Swift package/distribution lines as one compatible release set and keep Mappls symbols behind testable Swift protocols.
From2 source lines
EvidenceSelection Required
mGIS and GeoAnalytics workspace generation
Contain legacy mGIS API/library contracts behind a durable workspace seam, then select the entitled current dataset, web-method, analysis, and deployment surfaces without inventing replacement endpoints.
From1 source line
EvidenceSelection Required
Workmate and workforce journeys
Reframe deprecated Workmate surfaces around durable workforce aggregates, then select the entitled Mappls modules that satisfy each complete journey.
Cannot find a direct successor?
That is a decision point, not a documentation gap to hide.
Selection-required tracks show adjacent capabilities and the precise evidence still needed. Use the source atlas and support escalation packet to resolve the product-owned contract before implementation.