Migrate from Road Runner to HighLevel

Road Runner trajectories (TrajectoryActionBuilder sequences) map to a HighLevel custom object named Trajectory. Each trajectory's name, waypoints, and start/end poses are stored as separate custom fields within this object. The associated opmode reference is preserved as a text field so you can trace which program uses each trajectory. Custom field types include text for the trajectory name and opmode reference, numeric fields for waypoint count, and datetime fields for original creation timestamps.

Road Runner Pose2d coordinates (x, y, heading) and Pose3d (with z) are decomposed into separate numeric custom fields in a HighLevel Pose custom object. Each Pose links back to its parent Trajectory via a lookup relationship. Heading values are stored in degrees.

Road Runner MotionProfile constraints including max velocity, max acceleration, and max angular velocity are stored as individual numeric custom fields within a HighLevel Motion Profile custom object. Each Motion Profile record establishes a lookup relationship to the Trajectory records that reference it, preserving the constraint-to-trajectory association in the target system.

Road Runner TrajectorySequence objects (multi-trajectory sequences chained together) are stored as a HighLevel custom object. The sequence is represented as a JSON-serialized list of trajectory references stored in a custom long-text field, with step order preserved as an integer field.

Road Runner action-builder actions tied to opmode lifecycle events are translated into HighLevel Tasks. The action name becomes the task subject; the triggering opmode name is stored in the task description. Task due dates are inferred from the opmode schedule if present in the source.

Road Runner drive constants (wheel constants, feedforward gains, sensor calibration values) are stored as a HighLevel custom object with multiple numeric fields. HighLevel does not have a native equivalent — custom fields are required. These are linked to the relevant robot profile record.

Road Runner opmode files (autonomous/teleop programs) are treated as a high-level operational unit and mapped to HighLevel Opportunities. The opmode name becomes the Opportunity name; the opmode type (auto vs. teleop) maps to the Opportunity stage. Pipeline stages in HighLevel represent opmode categories.

Road Runner robot configurations (hardware definitions, motor assignments, sensor mappings) are treated as organizational units and mapped to HighLevel Companies. The robot name becomes the Company name; motor count and sensor count are stored as custom fields on the Company record.

Road Runner's git repository owner and team contributors are mapped to HighLevel Users by email match. Contributors without a HighLevel user account are stored as Contacts with a custom field indicating their repository role. This enables ownership attribution on trajectory records.

Git-based trajectory revision history (commit messages, timestamps, author) is translated into HighLevel activity notes on the relevant Trajectory custom object. Each revision becomes a separate Note record with the git commit message as the body and the commit timestamp as the note date.

Road Runner trajectory tags identifying robot type, competition class, and tuning status are mapped directly to HighLevel Tags applied to the Trajectory custom object. Tag labels are preserved verbatim during migration so filtering, segmentation, and reporting in HighLevel function immediately after cutover without requiring manual re-tagging.