Migrate your Road Runner data

RoadRunner has no native Contacts object — contact records are stored in a custom KV store namespace. We read from the configured storage backend and map fields to the destination CRM's contact schema, handling nulls and missing fields explicitly.

Company records are stored as JSON blobs in RoadRunner's KV store. We parse these blobs, normalize field names, and write to the destination platform's account or company object.

Work Orders are stored in the Jobs plugin queue rather than a dedicated table. We export queue state, metadata, and payload, then reconstruct Work Order records in the target FSM platform.

RoadRunner's Jobs plugin is a first-class object with its own queue, driver, and pipeline concept. We can read queue state and replay or redirect jobs to the destination system.

The KV plugin exposes a key-value interface used by most RoadRunner deployments to store application state. We export all namespaces and keys, preserving TTL metadata.

Technician profiles are stored in custom KV namespaces. We map these to the destination FSM's user or technician object, including role and territory assignments where present.

RoadRunner does not expose a centralized attachment store. Files referenced by jobs or KV records are external to the platform and must be migrated separately from object storage.

Locks are an in-memory distributed primitive for concurrency control, not a data object. They have no persistent state to migrate.

Metrics are ephemeral runtime telemetry aggregated by the Metrics plugin. They are not persisted as migratable records.

RoadRunner's pipeline definitions (for the Jobs plugin) are configuration files. We export these as JSON and convert pipeline step definitions to equivalent destination workflow triggers.