Beta release The ArcGIS Velocity Migration Tool is currently available in beta. While it is designed to support migration workflows, some components or configurations may not translate exactly between systems. We encourage you to review migrated content and provide feedback to help improve compatibility and overall experience. Functionality and behavior may be refined prior to general availability.
Use this guide to sign in, assess a GeoEvent Server XML export, download migration artifacts, and understand how the tool classifies items for ArcGIS Velocity migration planning. The migration assessment is deterministic; analysis runs entirely in the browser and produces an interactive HTML migration guide along with a Velocity JSON configuration for components that map automatically.
Browser-first processing The selected GeoEvent XML is parsed, mapped, and rendered in your browser. It is never uploaded to a server. The server delivers the application shell, hosts the OAuth callback, and serves this user guide — it does not see your configuration, perform any analysis, or generate any documents. The tool does not use AI, LLMs, or model training.
Support & feedback This tool is maintained by the ArcGIS Velocity Product Team and is not supported by Esri Technical Support. For questions about the tool or to report a problem, use the feedback repository and its community discussions. Esri Technical Support can still help with the underlying products and content — such as exporting your GeoEvent Server configuration, importing the generated ArcGIS Velocity configuration, or troubleshooting items after they have been imported into Velocity.
Knowing the target Velocity platform in advance helps the tool surface the right compatibility notes. The two supported targets are ArcGIS Velocity for ArcGIS Online and ArcGIS Velocity for ArcGIS Enterprise.
Sensitive content The exported XML may include service URLs, account names, internal hostnames, field names, and credential-shaped values. Treat it as customer-controlled sensitive data. Credential-like values are redacted in generated migration artifacts and must be re-entered directly in Velocity after import.
The migration workflow is gated behind ArcGIS OAuth sign-in. Sign-in uses the standard ArcGIS REST JS browser OAuth flow. No credentials, tokens, or account metadata are included in generated migration artifacts.
https://myportal.example.com/portal.ArcGIS Online sign-in uses a pre-registered application baked into the deployment, so no per-user registration is required. ArcGIS Enterprise sign-in requires that an administrator register the tool as an application on the target Portal and provide the Client ID to end users.
If a Portal application has not yet been registered, open the Enterprise Sign In dialog and expand More details to see the redirect URI the tool expects. Register the application as Other Application, add the redirect URI shown, then paste the generated App ID into the Client ID field.
Allowed redirect URI
The redirect URI is unique to the deployment origin and base path (for example
https://<host>/<base>/auth/callback, such as
https://<host>/migration/auth/callback). Use the exact value shown in
the sign-in dialog so the OAuth round-trip succeeds.
Browser prompt: “access other devices on your local network” If your Portal is hosted on a private or internal network, Chromium-based browsers (Google Chrome and Microsoft Edge) may show a one-time prompt asking whether to allow or block access to devices on your local network the first time you sign in. This is expected behavior in these environments — the browser is confirming the sign-in request to your internal Portal. Choose Allow. If the page fails to load the first time after allowing, sign in again and the sign-in will complete. Firefox does not show this prompt, and Portals reachable over the public internet are not affected.
After sign-in, the migration workflow is presented as a three-step wizard. You can move forward and back between steps; each step preserves earlier selections until you generate the final report.
The component summary card shown after upload lists how many inputs, outputs, services, processors, filters, GeoEvent definitions, geofences, folder data stores, and ArcGIS Server connections were detected in the configuration.
File size guardrails The tool accepts XML configurations up to 100 MB. Internally, no single XML text node may exceed 5 MB and total text content across the document is capped at 50 MB; both are XML-security limits and well above anything a real GeoEvent Server export produces. Geofence-heavy configurations (tens of thousands of imported geofences) are supported — the migration report summarizes them by category rather than listing each individually.
Both target-platform and strategy selections affect compatibility verdicts. For example, a connector may be available for Enterprise but require redesign for Velocity for ArcGIS Online; the report calls these differences out per component.
What the URL verification toggle does
When on, requests are made anonymously (credentials: 'omit') over HTTPS and
only target hosts already named in the configuration. Private, loopback, link-local,
and cloud-metadata destinations are blocked before any request is issued. No credentials
are sent and no data is exfiltrated; the only outbound traffic is the GET to each
referenced ArcGIS REST endpoint.
The results step presents the migration report inline as interactive HTML. From this step you can:
.html file you can archive, email, or open offline.Download before leaving the page Generated artifacts are produced as in-memory blobs and offered through ephemeral object URLs. Closing the browser tab clears all in-flight migration state, so download any artifacts you want to keep before you leave. To revisit results later, re-upload the GeoEvent XML and run the assessment again.
The HTML migration guide is the primary output. It is rendered entirely in your browser and contains the executive summary, full component tables, warnings, linked navigation, and flow diagrams (as inline SVG) for each mapped service. From the results page, choose Open Migration Guide (HTML) to view it in a new tab.
Choose Download Migration Guide (HTML) on the results page to save the
same guide as a self-contained .html file. The download is generated
in-browser — styles, scripts, and diagrams are inlined — so the file works offline and
can be opened, shared, or attached to a ticket without any server connectivity.
For components that have a direct Velocity equivalent, the tool emits a Velocity JSON definition you can import or stage in Velocity. Items with no equivalent or items that require manual review are not included in the JSON output but are documented in the report so an administrator can act on them.
Validate in a non-production Velocity environment Always import the generated Velocity JSON into a staging Velocity environment before rolling out to production. Verify feature layer schemas, Track ID fields, time settings, geometry settings, and update behavior.
Every detected component is classified into one of four compatibility categories based on the functional matrix. The category drives how prominently the item appears in the report and whether it shows up in the Velocity JSON output.
The functional matrix is the authoritative source of truth for component mapping. It records, for each GeoEvent component type, the Velocity equivalent, target-platform support, migration notes, limitations, parameter mappings, alternatives, and recommended manual actions.
The matrix is shipped with each release and is versioned along with the tool. When the matrix changes (for example, when a Velocity feature becomes generally available), the report you generate for the same XML may also change.
| Source area | What it covers |
|---|---|
| Inputs & outputs | Connectors and transport equivalents (REST, Kafka, RabbitMQ, MQTT, file watchers, etc.). |
| Processors | Filter, enrich, calculate, geotag, incident, and spatial processors mapped to Velocity analytics. |
| Services | End-to-end GeoEvent Services mapped to Velocity feeds and real-time / big-data analytics. |
| Stores & connections | Folder data stores, ArcGIS Server connections, and registered feature layer endpoints. |
| Definitions & geofences | GeoEvent definitions, schema mappings, and geofence collections referenced by services. |
The tool is designed for browser-first, deterministic processing. A short summary of the posture:
localStorage by ArcGIS REST JS for sign-in restoration only.The redirect URI registered on your Portal application probably does not match the deployment origin and base path. Open the Enterprise Sign In dialog, expand More details, copy the shown redirect URI, and add it to your Portal app's allowed redirect URIs. ArcGIS Online sign-in uses a pre-registered application, so this normally only applies to Enterprise sign-in.
If your ArcGIS Enterprise Portal is on a private or internal network, Chromium-based browsers (Google Chrome and Microsoft Edge) show a one-time prompt asking to allow or block access to devices on your local network the first time you sign in. This is expected behavior in these environments. Select Allow; if the page fails to load the first time after allowing, sign in again and the sign-in will complete. Firefox does not show this prompt, and Portals reachable over the public internet are not affected.
The exported file may have been truncated or modified. Re-export from GeoEvent Manager and try again. The tool will reject files that are not well-formed XML or that contain XML external entity declarations.
The configuration exceeds one of the tool's hard limits: the file is larger than 100 MB, a single XML text node is larger than 5 MB, or total text content exceeds 50 MB. Real GeoEvent Server exports rarely approach any of these limits. If you encounter this with an unmodified export, confirm the file came directly from GeoEvent Manager rather than a synthetic or test-generated source.
The configuration was parsed successfully, but no input components matched a Velocity feed equivalent for the selected target. Switch to the other target platform to see if the matrix has equivalents for that environment, or review the input components in the report for redesign notes.
Open the HTML migration guide in a new tab (or open a previously downloaded
.html file) and use your browser's Print → Save as PDF
command. The guide includes print styles that collapse the interactive toolbar,
sidebar, and diagram controls so the printed copy is clean and self-contained.
The deployment uses a nonce-based Content Security Policy that blocks inline scripts. Browser extensions that inject scripts or styles can trigger these warnings without affecting the tool. If you see violations from the application itself, capture the full message and contact your deployment administrator.
No. The XML is read with the File API and parsed in a Web Worker inside your browser. The server has no upload endpoint and never sees your configuration. All artifacts — the interactive HTML guide, the downloadable HTML guide, and the Velocity JSON — are produced entirely in the browser.
No. The migration analysis is fully deterministic and driven by a static functional matrix. Selected configurations and generated artifacts are not used for AI or model training.
No application-side credential store exists. ArcGIS OAuth session material may be
kept in browser localStorage by ArcGIS REST JS so you don't have to sign
in repeatedly. Credential-shaped values inside the XML (passwords, tokens, API keys,
authorization headers, sensitive query parameters) are redacted from every generated
artifact and must be re-entered in Velocity.
Choose the target you intend to deploy to. Some components map differently for Velocity for ArcGIS Online than for Velocity for ArcGIS Enterprise. If you are evaluating both, run the report twice, once per target, and compare the verdicts.
Yes. Use the Back button in the wizard to return to Step 2, change the target or strategy, and regenerate. The previously uploaded XML stays loaded in browser memory until you leave the page.
Only items the matrix classifies as fully compatible (and a subset of partially compatible items for which a deterministic mapping exists) appear in the JSON. The report documents items that require manual action so you can address them in Velocity directly.
The functional matrix is updated as Velocity evolves. A component that previously had no equivalent may become fully compatible, or migration guidance may be revised. See the Changelog for the relevant release entry.
Generated artifacts may contain migration-relevant settings from your source configuration. Review them before sharing outside the authorized migration team and follow your organization's data-handling policy.
The current release of Chrome, Edge, Firefox, and Safari. The tool relies on modern File API, Web Worker, and Calcite Components support; older browsers may not be able to load the wizard.
Migration analysis and all downloadable artifacts are produced in the browser. Once the application page has loaded, an analysis run can complete and produce its outputs without further network access. ArcGIS sign-in still requires connectivity to the Portal you are signing in to. A downloaded HTML migration guide is fully self-contained and opens offline from your file system.
User-visible changes to the migration tool.