Migrate from Eagle CRM to Freshsales

Property and listing custom objects have no Freshsales standard equivalent

Eagle CRM's real-estate-specific Property and Listing objects store property IDs, listing statuses, and property-type fields that don't map to any Freshsales standard object. Freshsales Custom Objects API can model these but require pre-creation of the object schema (label, name, field definitions) before data can be inserted. FlitStack AI delivers a Custom Object setup plan as part of the migration package — your Freshsales admin creates the object in the UI first, then we load the data via the API. The Property-to-Contact and Property-to-Account association links use Freshsales' N:1 relationship model, which differs from Eagle CRM's flexible linking. We document the junction mapping explicitly before the full run so the association logic is preserved.

Eagle CRM global pipeline stages must be split per Freshsales pipeline

Eagle CRM stores pipeline stages as global values across all pipelines, meaning one stage name can appear in multiple pipelines with the same label but different meanings. Freshsales scopes stage values to individual Sales Pipelines — each pipeline can have its own set of stage values with independent probabilities and forecast categories. This means an Eagle CRM pipeline with three stages generates a separate stage value-mapping table per destination pipeline in Freshsales. If your Eagle CRM has five pipelines with overlapping stage names, Freshsales will show five separate stage sets in the UI. FlitStack AI surfaces the per-pipeline mapping table during the planning phase so there are no surprises at go-live.

Eagle CRM API rate limits constrain delta-pickup window length

Eagle CRM's REST API enforces per-day request limits that vary by plan tier. For large datasets, repeated API calls during the delta-pickup phase can exhaust the daily limit before all modified records are fetched. Freshsales also has its own API rate limits during the bulk insert phase. FlitStack AI monitors both sides in real time: if the Eagle CRM read limit is reached mid-delta, we pause and resume on the next available window rather than dropping records. For migrations exceeding 200,000 records, we recommend a 72-hour delta window and a pre-migration data freeze coordination to ensure the delta volume stays within API budget.

Workflows, automation rules, and sequence logic do not migrate

Eagle CRM's listing-update rules, automated task-assignment workflows, and follow-up sequences are logic constructs stored in the Eagle CRM workflow engine with references to internal object IDs. Freshsales Workflows use a completely different rule structure (trigger-action model with Freshsales-specific field references). There is no migration path: workflow logic must be rebuilt in Freshsales. FlitStack AI exports your Eagle CRM workflow definitions as a structured reference document so your Freshsales admin has the rule intent documented. Note that any workflow referencing a custom field (Property_ID, listing_status) will also need the Freshsales custom field created first — we coordinate the rebuild sequencing.

Property attachments re-uploaded; inline images in notes require extraction

Eagle CRM property photos and listing documents are binary blobs associated with the Property object. Freshsales Files attach to Contact, Account, or Opportunity records — there is no native File attach to Custom Object records. For property photos, we attach them to the primary Contact or Account associated with that property listing. PDF listing documents are re-uploaded as Freshsales Files linked to the same record. Notes with inline images (HTML img tags referencing Eagle CRM-hosted URLs) are extracted: images download locally and re-upload to Freshsales Files, then the note body is updated with the Freshsales-hosted URL. This step adds processing time for migrations with heavy attachment volume.