Migrate from Followup CRM to Zoho CRM

Followup CRM contacts migrate as Zoho CRM Contacts. Each contact is created with first name, last name, email, phone, and job title. If the contact has no associated company in Followup CRM, it lands as an orphan Contact in Zoho — no default account assignment is performed.

Followup CRM contacts flagged as prospects without a closed deal can be routed to Zoho Leads instead of Contacts. The split decision is configurable — either all Followup CRM contacts go to Zoho Contacts, or contacts with no associated deal history route to Zoho Leads for re-qualification.

Followup CRM companies map directly to Zoho CRM Accounts. Account Name, Website, Industry, Employee Count, and Annual Revenue carry over as standard Account fields. Parent‑child company hierarchies in Followup CRM are preserved using Zoho's Account Hierarchy feature, and any custom fields on the Company object are created as Zoho custom fields before the migration loads. Address information and validation rules are applied during import to catch missing required values.

Followup CRM deals map to Zoho CRM Deals. Deal Name, Amount, Closing Date, and Owner are direct mappings. Pipeline and Stage are mapped via value mapping (see field_mapping), with each Followup CRM pipeline requiring a corresponding Zoho Deal layout. Deal custom fields are created in Zoho before the load, and any stage‑transition timestamps from Followup CRM are stored as custom datetime fields for audit continuity.

Followup CRM pipelines have no direct Zoho CRM equivalent — Zoho scopes Deal Stages per layout and per Blueprint process. Each Followup CRM pipeline becomes a Zoho CRM Deal Layout, and the pipeline's stage order is recreated as the layout's stage sequence. If Followup sequences drive workflow triggers, these are documented for Blueprint rebuild.

Stage names map value-by-value. Zoho CRM stage values are defined per layout, so FlitStack maps each Followup CRM stage label to the matching Zoho stage pick-list value. Unmatched stage names are flagged before migration; your Zoho admin creates the target stage values first.

Followup CRM tasks migrate as Zoho CRM Tasks. Subject, Due Date, Status, and Priority carry over. The original task owner is resolved by email match against Zoho CRM users; unmatched owners are flagged and assigned to a fallback owner before the migration commits.

Followup CRM events (meetings, calls, appointments) migrate as Zoho CRM Events. Start Time, End Time, Location, and Description are preserved. Recurring events are squashed into single entries during migration per Zoho Bulk API limitations — recurring event logic should be rebuilt in Zoho Calendar.

Followup CRM notes migrate as Zoho CRM Notes. Note Title, Body, and the parent record link (Contact, Company, or Deal) carry over. Plain-text formatting migrates cleanly; rich-text HTML is stripped to plain text since Zoho Notes does not render HTML.

Followup CRM file attachments are downloaded from the source, re-uploaded to Zoho CRM's Documents module, and linked back to the parent record via a URL or File Upload custom field. Files exceeding Zoho's attachment size limit (25 MB per file) are flagged for manual handling.

Followup CRM custom fields on Contacts, Companies, and Deals are read from the API response and created in Zoho CRM with the matching data type before data loads. Pick-list custom fields require value mapping; multi-select fields are stored as comma-separated strings in Zoho text fields.

Followup CRM's follow-up scheduling rules and sequence logic have no Zoho CRM equivalent. We export the sequence definitions (step order, delay rules, task templates) as a structured JSON document. Your Zoho admin uses Blueprint and Workflow Rules to rebuild equivalent sequences in Zoho.

Followup CRM owner IDs are resolved against Zoho CRM users by email address match. Active Followup CRM users without a corresponding Zoho user are flagged before migration — either invite them to Zoho first or assign their records to a fallback Zoho user owner.