Migrate from Road Runner to Salesforce Sales Cloud

Road Runner quote headers map 1:1 to Salesforce Opportunity records. Quote name, total amount, and status fields map to Opportunity Name, Amount, and StageName. Owner resolution happens by email match to Salesforce users before records insert. All Road Runner timestamps are preserved in custom datetime fields on the Opportunity record to maintain historical reporting continuity and audit trail integrity across the migration.

If the destination org uses Salesforce native Quotes, Road Runner quote documents map to the Salesforce Quote object. Quote expiration date, description, and billing/shipping terms migrate as Quote fields. Approval state flag migrates as a custom field since Salesforce Quote approval is a separate configuration.

Road Runner product definitions with pricing tiers map to Salesforce Product2 records plus PricebookEntry records tied to the standard or custom pricebook. Unit price and pricing model type (one-time, recurring, usage) translate to PricebookEntry.UnitPrice and subscription fields. Pricing tier metadata is preserved as custom fields on the Product2 record to maintain tiering structure, and each PricebookEntry references the appropriate pricebook ID for the destination org.

Road Runner configuration bundles — parent product with mandatory or optional child products — split into OpportunityLineItem records. Bundle metadata (mandatory/optional flags, quantity rules) are stored in custom fields on the line item or a junction object to preserve the bundle hierarchy in Salesforce.

Road Runner pricing rule conditions (discount tiers, volume breakpoints, customer-type discounts) translate to a combination of custom fields on OpportunityLineItem capturing rule metadata, plus a Salesforce Flow that evaluates the condition at quote-generation time. If destination has CPQ, conditions map to CPQ Pricing Rules.

Road Runner approval-state field (pending, approved, rejected) migrates as a custom pick-list field on the Quote object. Salesforce approval routing requires manual configuration in Salesforce Approvals or CPQ Approvals — we provide a mapping of approver-role names to Salesforce roles as a rebuild reference.

Road Runner accounts map directly to Salesforce Account records. Account name, industry, website, and billing address migrate as standard Account fields. Multi-address records collapse to the primary billing address with secondary addresses stored in custom fields. Owner assignments are resolved via email matching against Salesforce users prior to migration to ensure accountability and proper sharing model activation.

Road Runner contact records map to Salesforce Contact objects. First name, last name, email, phone, and title migrate as standard fields. Contacts without a primary account link attach to a default 'Unassigned Account' record to satisfy the required AccountId lookup.

Road Runner deals or opportunities tracked outside the CPQ flow map to Salesforce Opportunity records using standard stage, amount, close date, and owner fields. Pipeline and stage mapping uses Salesforce Sales Processes tied to record types if the org uses multiple deal types.

Road Runner custom fields on quotes (region codes, contract-type flags, internal references) that have no Salesforce standard equivalent require custom field creation on the Quote or OpportunityLineItem object before migration. We deliver a custom field specification sheet as part of the pre-migration schema plan.

Road Runner related-product links (cross-sell, upsell, substitute) translate to a custom junction object or custom fields on OpportunityLineItem depending on the relationship type. N:N product relationships in Road Runner require junction objects in Salesforce. Relationship metadata including effective dates, priority flags, and cross-sell sequences are preserved in custom fields to maintain full business context during the transition.

Road Runner attached documents on quotes or products re-upload to Salesforce Files linked to the corresponding Opportunity or Quote record. File size limits (Salesforce default 25MB per file) are enforced; files exceeding the limit are flagged for manual transfer. Version history and original file names are preserved where available, with each document linked to its source quote or product for full traceability and audit compliance.