Migrate from improveit 360 to Freshsales

Improveit 360 leads map directly to Freshsales Lead records. The lead's status, source, and owner are preserved as standard Freshsales Lead fields. Any Improveit 360 custom fields on the lead object become Freshsales custom fields created before the import runs.

When an Improveit 360 record's status field indicates a closed‑won deal or a specific customer‑lifecycle value, FlitStack routes that record to a Freshsales Contact instead of a Lead. This follows Freshsales' Lead‑to‑Contact conversion logic, preserving the original status, owner, and any associated custom fields during the import.

Improveit 360 company records map to Freshsales Account. Company name, address, phone, website, and industry all have direct Freshsales equivalents. Industry values that don't match Freshsales' picklist are stored as a custom field or mapped to the nearest standard value at migration time.

Improveit 360 deals migrate to Freshsales Deals. Deal name, amount, stage, close date, owner, and associated company are mapped field-by-field. Improveit 360 pipeline stages are mapped to Freshsales Deal stages — if multiple pipelines exist, each becomes a separate Freshsales deal pipeline.

Improveit 360 product catalog items and quote line items migrate as Freshsales Products. Product name, description, unit price, and SKU are mapped directly. Bundle or assembly products in Improveit 360 that have sub-items are stored as separate Products and linked by a custom relationship field in Freshsales.

Improveit 360 appointment records convert to Freshsales Events. Original start time, end time, location, assigned user (owner), and associated contact or deal are preserved. Production-grid-specific fields (crew assignment, scheduling slot type) that have no Freshsales equivalent are stored as custom fields for reference — the scheduling workflow must be rebuilt using Freshsales Calendar or a third-party scheduling tool.

Improveit 360 tasks and logged activities (call logs, follow-up reminders, internal notes) migrate as Freshsales Tasks. Task subject, due date, status, owner, and linked contact or deal are preserved. Timestamps for when the activity was created in Improveit 360 are kept for audit continuity.

Improveit 360 notes and attached documents migrate to Freshsales Notes. Plain-text notes map directly; any formatted content is preserved as-is. File attachments are downloaded and re-uploaded to Freshsales Files with the original file name and timestamp preserved. File size limits on the Freshsales import are respected — large files are chunked or linked.

Improveit 360 user accounts are matched to Freshsales users by email address. Unmatched owners are flagged in the migration report — your Freshsales admin either creates the user first or assigns the records to a fallback owner before the migration runs. Active/inactive status is preserved where possible.

Any Improveit 360 custom field — including construction-specific fields like job_type, project_template_id, or crew_id — is migrated as a Freshsales custom field on the equivalent object. Freshsales custom fields are created via the UI or API before the data import begins so values land in the correct columns.

Improveit 360 workflows (automated follow-up sequences, appointment reminders, lifecycle email campaigns) do not migrate. FlitStack exports the workflow definitions in a structured JSON format so your Freshsales admin or implementation partner can reference them when rebuilding automations in Freshsales' Workflow builder.

Improveit 360 saved reports and dashboards are not migrated. The underlying data (deals, tasks, contacts, activities) does migrate to Freshsales, so you can recreate reports using Freshsales' built-in reporting or connect to a BI tool. We provide a data dictionary mapping each Improveit 360 report field to its Freshsales equivalent to accelerate report rebuilding.