Migrate from Oncord to Freshsales

Oncord Contacts map directly to Freshsales Contacts. We extract all standard contact fields (name, email, phone, address, job title) via Oncord's CustomFields API component and import into Freshsales via CSV using email as the dedupe key. Oncord's contact owner assignment maps to Freshsales OwnerId resolved by email match against the destination User table. Historical timestamps (created_date, updated_date) preserve on the Contact record.

Oncord Groups are static tagging and segmentation lists. We export all Group names and membership records and map them to Freshsales Segments on the Contact object. Each Oncord Group becomes a Segment with the same name, and membership is recreated as Segment-to-Contact assignments. On Lite plans, Oncord restricts filters to Groups only, which increases the importance of these lists; we confirm the active plan tier during scoping because Lite plan groups may be the only segmentation data available.

Oncord CustomFields are read via the CustomFields API component. We export field definitions (name, type, options) and values per Contact record, then create matching custom fields in Freshsales on the Contact object using the Freshsales API or admin interface. Type mapping: Oncord text, number, date, and dropdown types map to Freshsales Text, Number, Date, and Picklist custom fields respectively. On Lite plans, custom fields are supported but the overall data scope is restricted; we confirm which fields have populated values during scoping.

Products are only available when the Commerce add-on ($40/month) is active. We export product name, description, price, SKU, inventory count, images, and custom product fields via the Oncord export. Products map to Freshsales Product records with Standard Price Book entries created during import. SKUs map to product_code. If the customer does not have the Commerce add-on active, no product data exists to migrate and we exclude this object from scope. On Lite plans, Commerce is limited to 15 products; we confirm the active product count during discovery.

Oncord Events include event name, date, location, capacity, and RSVP attendee list linked to Contacts. We export events and attendee records via the Oncord backup. Each event migrates as a Freshsales Event with date and location preserved; attendee RSVPs map to EventRelation records linked to the corresponding Freshsales Contacts. Oncord does not expose a formal Events API, so export completeness depends on what Oncord's backup contains. We flag any missing event data in the pre-migration audit.

Oncord includes unlimited admin users on base plans. We export user records including name, email, and role (admin, staff, customer). Owner assignment on Oncord Contacts maps to Freshsales User records resolved by email match. Role semantics differ between platforms: Oncord uses platform-level roles while Freshsales uses Salesforce-style profile and role hierarchy. We document the mapping and flag any admin users who may need Freshworks account provisioning before migration.

Oncord Marketing automation workflows trigger on contact activity, group membership, or time-based schedules. We do not migrate workflows as code because Oncord's undocumented automation engine has no exportable format. We document every active workflow's trigger, conditions, actions, and target audience in a written inventory delivered to the customer's admin for rebuild in Freshsales Workflows (Pro and above) or Freshmarketer sequences. Scoping confirms whether the Marketing add-on is active; Lite plans have no automation capability.

Oncord web forms capture contact data and may carry custom field mappings per form. We export form definitions and field-to-contact-property mappings so the customer can rebuild equivalent forms in Freshsales using Web-to-Lead or a third-party form builder. Form submission history does not migrate as records; the migrated Contacts reflect the current state of the database. If the Marketing add-on is not active, no form data exists to document.