Migrate from Vaulta to Freshsales

Vaulta person records split based on qualification status: unqualified Vaulta contacts with no deal association migrate to Freshsales Lead. Vaulta contacts associated with a deal or marked as a customer migrate to Freshsales Contact. The split rule is configurable — your team chooses the threshold based on Vaulta's status field values.

Vaulta company records map directly to Freshsales Account. Company name maps to Account Name, domain to Website, industry pick-list to Industry field with value-by-value mapping. Vaulta parent-child company hierarchies map to Freshsales Parent Account lookup; circular references are flagged and resolved by FlitStack before the migration run.

Vaulta deal records map to Freshsales Deal. Deal name, amount, close date, and owner email transfer directly. Vaulta deal stage names map to Freshsales pipeline stage names — each Vaulta pipeline becomes a Freshsales pipeline. Multiple Vaulta pipelines require multiple Freshsales pipelines to be configured before data lands.

Each Vaulta deal pipeline becomes a Freshsales named pipeline. Freshsales pipeline configuration is a prerequisite — FlitStack delivers a pipeline setup plan that maps Vaulta pipeline names and stage counts to Freshsales pipeline and stage creation steps so the schema is ready before migration validation runs.

Vaulta call logs migrate as Freshsales Tasks with Type set to 'Call'. Subject, duration, outcome, notes, original timestamp, and owner email are preserved. Freshsales call logs created via built-in phone also create Task records — the migration aligns both patterns.

Vaulta email activity records migrate as Freshsales Tasks with Type set to 'Email'. Subject line, body preview, timestamp, and owner are mapped. HTML email body is stored as a custom field or attachment to preserve formatting when plain-text mapping is insufficient.

Vaulta meeting records map to Freshsales Events. Start time, end time, location, title, description, and attendees transfer. Owner resolution by email match applies to meeting records the same way it applies to contacts and deals. If the meeting includes external participants not present in Freshsales, FlitStack creates placeholder contacts or links them to existing records based on email addresses to maintain a complete attendee list.

Vaulta note records migrate to Freshsales Notes. Rich-text formatting is preserved where Vaulta and Freshsales both support HTML note bodies. Plain-text notes transfer as-is. Note attachments re-upload as Freshsales file attachments. For notes containing embedded images or linked files, FlitStack extracts those assets, stores them in Freshsales's file repository, and updates the note body to reference the new file URLs so the visual context is retained.

Vaulta custom objects migrate to Freshsales Custom Objects 1:1. Freshsales Custom Objects (Enterprise plan feature) support custom fields, relationships, and reporting — your Vaulta custom object schema is recreated in Freshsales before migration validation. Custom object associations requiring junction behavior are surfaced in the migration plan.

Vaulta owner IDs resolve to Freshsales users by email address match. Vaulta user email addresses are matched against Freshsales user accounts. Unmatched owners are flagged in the pre-migration audit — your Freshsales admin either invites them to Freshsales or assigns their records to a fallback owner before the migration run commits.

Vaulta file attachments on contacts, companies, and deals re-upload to Freshsales as file attachments on the corresponding records. File size limits apply: Freshsales enforces 25MB per file on most plans. Inline images embedded in note bodies are extracted and re-hosted as Freshsales file attachments.