Honua
// migration

Assess → Pilot → Validate → Move.

Migrate one representative workflow at a time. Honua automates repeatable import and source changes, then flags the remaining patterns for review. Keep the current platform live, compare both paths side by side, and move the endpoint only when the workflow passes.

Scope a migration pilot Check compatibility →
one service · side-by-side pilot
CURRENT existing service stays live
PILOT Honua runs beside it
 
CHECK ArcGIS Pro opens the map
CHECK QGIS draws the expected layer
CHECK auth · edits · performance
 
MOVE update the route after the checks pass
// side-by-side migration

Four decisions. No big-bang cutover.

The current platform stays available through the pilot. Each workflow earns its move with real client and response checks.

01 · ASSESS
Choose the workflow.
Inventory its services, clients, data, authentication, and required operations. Define the checks that prove it still works.
02 · PILOT
Build beside production.
Import one representative service, run supported source rewrites, and point a test client at Honua while the existing endpoint stays live.
03 · VALIDATE
Compare both paths.
Test responses, rendering, editing, security, and performance with the real client and workflow.
04 · MOVE
Switch when it passes.
Repoint the client or route, keep a rollback path, and repeat with the next workflow.
// automation + review

Honua handles the repeatable work and shows you the rest.

Every automated path produces an explicit plan or report. Your team keeps control of the changes that need judgment.

AUTO
Automates
imports · catalog plans · JavaScript rewrites
repeatable
  • Imports selected FeatureServer and MapServer layers into PostGIS and publishes them.
  • Scans a GeoServer catalog, generates a dry run, and applies bounded catalog entries for existing target tables.
  • Rewrites supported ArcGIS JavaScript imports, constructors, query options, watches, and events to @honua/sdk-esri-compat.
Run reports make every automated change visible.
FLAG
Flags for review
TODO markers · readiness report · operator choice
review
  • Records detected source usage, completed rewrites, and remaining patterns in the run report.
  • Adds TODO(honua-migrate) markers where the JavaScript codemod cannot make a safe change.
  • Leaves the team to adapt, replace, or defer each flagged pattern before validation.
Python scan / translate / run tooling is available from source. .NET and MAUI use guided adapter paths.
// manual review

What still needs review.

Keep these items inside the pilot.

At cutover, repoint each map or app to Honua, or preserve the public URL through your gateway when your routing setup allows it. Your team runs this step and reviews unsupported renderers, external symbols, attachments, unrecognized code, GeoServer feature-data copying, unsupported stores, and lossy SLD conversions. .NET and MAUI applications use guided adapters instead of automatic source rewrites.

See the side-by-side Esri migration architecture →
// keep reading
std Compatibility Documented GeoServices and OGC surfaces, with operation-level evidence for the client workflows your team must preserve. Read compatibility ops Operations Use familiar health, telemetry, and Git-reviewed release practices. Read operations $ Pricing A flat annual license priced by capacity, with no named-user seats, request credits, or data-volume billing. Read pricing
// next

Pilot one workflow.
Move when it passes.

Scope a migration pilot Try the JavaScript codemod ↗