Migrate from Road Runner to Zoho CRM

Zoho Contact records store name, email, phone, and title. Contacts without a primary company land as orphan records; FlitStack attaches them to a placeholder Account record and flags them for review. Owner resolution uses email-to-User_ID matching against Zoho's user directory.

Road Runner contacts without a closed-won deal or with a lead-status flag migrate as Zoho Leads. Leads with a qualifying deal convert to Contacts during migration using Zoho's Convert Lead API, consuming 5 API credits per record, and ensures proper pipeline attribution after conversion.

Account is Zoho's company module. Parent-child company hierarchies map to the Parent Account lookup field. Multi-branch companies in Road Runner require flattening or custom sub-account handling — the migration plan flags this before records land. FlitStack documents each hierarchy transformation for audit trail.

Road Runner deal records map to Zoho Deals module. The Stage field maps via value-by-value pick-list matching. Deals must land after Accounts and Contacts resolve so the Account_Name lookup field is valid. If any account is missing, FlitStack creates a placeholder to prevent lookup failures.

Stage names and ordering preserved as Zoho Stage pick-list values. Probability percentages and forecast category are reapplied based on Zoho's stage settings. Zoho Blueprint stage gates require separate configuration after data lands. FlitStack provides a stage-mapping worksheet to expedite Blueprint setup.

Road Runner activity logs map to Zoho Tasks (calls and emails) and Events (meetings). Original timestamps, owner, and duration are preserved. Notes migrate as Zoho Notes with parent-record linkage; rich-text formatting is stripped if HTML markup is present. The migration also records the original activity type for reporting in Zoho Analytics.

Road Runner file attachments download and re-upload to Zoho as Attachments on the parent record. Zoho's 25MB per file limit applies; files exceeding this are flagged for splitting or alternative storage before migration. FlitStack logs each file transfer with checksum verification to ensure data integrity.

Zoho custom fields do not support multi-select pick-list in all modules. Multi-select values from Road Runner collapse to a comma-separated text field with a tooltip note indicating the original pick-list. This is documented in the migration plan before field creation.

Road Runner owner_id (email or name) resolves to a Zoho User_ID via directory lookup. Unmatched owners are flagged before migration; their records are assigned to a fallback Zoho user or left unassigned and flagged for manual assignment after go-live to preserve reporting accuracy.

Automations and workflows defined in Road Runner do not have a Zoho equivalent. FlitStack exports the workflow definitions as a structured JSON document and delivers a rebuild guide mapping each Road Runner trigger-action pair to Zoho Workflow Rules and Deluge functions.

Reports and dashboards reference Road Runner-specific field names and aggregations. The underlying data migrates; report logic must be rebuilt in Zoho Analytics using migrated field names. A field-name cross-reference document is delivered alongside the data migration. This ensures continuity of reporting during and after the transition.

Road Runner integrations (e.g., Zapier, Outlook sync, third-party dialers) have no Zoho counterpart and must be reconfigured. Zoho's Connections framework (OAuth-based) requires re-authentication and endpoint updates for each integration. FlitStack documents the current integration flow and provides a step-by-step setup guide for Zoho Connections.