Migrate from Road Runner to Freshsales

Road Runner team members with email addresses map to Freshsales users. Freshsales requires a valid user record for owner assignment on every CRM object. Email address is the primary match key; unmatched team members are flagged for admin action before migration runs.

Road Runner contact records migrate to Freshsales Contacts. Required Freshsales fields (first_name, last_name, email) are mapped directly from Road Runner properties. Records missing required fields are held and reported for manual correction before the migration commits. This validation ensures data integrity and prevents incomplete records from entering your Freshsales instance during the migration process.

Road Runner organization-type contact records map to Freshsales Accounts. Account name and domain are mapped to Freshsales' Name and website fields. Parent-child organization hierarchies in Road Runner map to Freshsales' Parent Account lookup where present. This hierarchical mapping preserves organizational relationships and enables proper account nesting within your Freshsales CRM structure.

Road Runner deal records migrate to Freshsales Deals. Deal name, amount, close date, and owner are mapped to Freshsales' deal_name, amount, close_date, and OwnerId. Pipeline and stage mapping requires Freshsales pipeline pre-configuration — we deliver the pipeline setup plan before data lands.

Road Runner pipeline definitions become Freshsales Sales Pipelines. Each Road Runner pipeline stage maps to a corresponding Freshsales stage within that pipeline. Stage names, probabilities, and forecast categories are mapped per the configuration plan delivered before migration begins. This ensures deal records land in the correct pipeline stages with proper probability assignments and forecast category classifications.

Road Runner activity logs migrate to Freshsales Sales Activities. Email activities become Freshsales email records, call logs become tasks with type='call', and meeting records become events. Original timestamps, owners, and parent-record links are preserved across all activity types. This comprehensive activity migration ensures your complete interaction history is maintained and accessible within Freshsales for future reference and follow-up activities.

Road Runner notes migrate to Freshsales Notes. Rich-text formatting is preserved where Road Runner stores it. Notes are linked to their parent record (Contact, Account, or Deal) using Freshsales' association model. This ensures all contextual information, comments, and documentation associated with each record is properly transferred and remains accessible within the appropriate record context in Freshsales.

Road Runner file attachments are re-uploaded to Freshsales Documents and linked to the parent record. Freshsales enforces a 25MB per-file limit — files exceeding this are skipped and logged with a warning. Large file strategy is agreed upon during discovery before migration runs.

Road Runner custom fields on any object migrate as Freshsales Custom Fields on the equivalent object. Field type is preserved where possible (text→text, number→number, date→date). Pick-list custom fields require value alignment between Road Runner and Freshsales — mismatched values are flagged for admin resolution before migration.

Road Runner workflows and sequences do not migrate. Freshsales has its own workflow builder for automation rules. FlitStack AI exports Road Runner workflow definitions as a reference document for the Freshsales admin to use when rebuilding automations manually after migration.