Migrate from Jiva to monday CRM

Jiva person records (name, email, phone, address, custom person properties) migrate to Monday CRM People items. The person's primary Jiva identifier is preserved as a custom text column for traceability and delta-run matching. All standard fields are mapped directly, and any missing contacts are flagged for manual review before the final migration run.

Jiva company records map to Monday CRM Organizations. Organization name, domain/website, industry, and employee count migrate as standard columns. Multi-contact associations collapse to the primary person record with secondary contacts linked via the Organization's person list. Any missing company data is noted for manual entry after cutover.

Jiva deal or case records become Monday CRM Deal items on the CRM board. The Jiva deal value, expected close date, and custom deal properties map to Deal Monetary Value, Expected Close Date, and custom columns respectively. Pipeline stage is reconstructed as a Status column with Jiva stage values as status labels.

Jiva stage or form-status pick-list values map one-to-one to Monday CRM Status labels on the CRM Deal board. Each Jiva stage value is created as a distinct status label; if Jiva uses numeric or coded stage names, a transformation column is added alongside the Status column for reference.

Jiva record types or custom forms that do not map to People, Organizations, or Deals are migrated as standalone Monday CRM boards. The board inherits the Jiva form's custom fields as columns with equivalent types. These boards can be linked to the main CRM workspace via board connections.

Jiva notes, call logs, and email references attached to a primary record migrate as Updates on the corresponding Monday CRM item. Timestamps and the creating Jiva user are preserved as update metadata. Longer activity narratives become sub-items with a Date column and description column.

Jiva file attachments are downloaded, re-uploaded to Monday CRM's file storage, and attached to the relevant item via the File column or as a sub-item with a file attachment. File size limits (up to 250 MB per file on Monday CRM) are respected; oversized files are flagged before migration.

Jiva users are matched to Monday CRM workspace members by email. If a Jiva user has no Monday CRM account, their name is stored in a text column and flagged; your admin creates the Monday CRM account and we re-assign ownership before cutover.

Jiva custom properties with non-text types (multi-select, date, number, checkbox) are created as Monday CRM custom columns of the equivalent type. Multi-select Jiva fields become Dropdown columns with the Jiva pick-list values pre-loaded as options. If a Jiva property uses a type not directly supported, we map it to a Text column and log the original type for future reference.

Jiva's original create date and last-modified date are preserved in custom Date columns on the Monday CRM item since Monday CRM's system Created Date reflects the migration import time. This preserves reporting continuity for historical analysis. The custom columns are labeled clearly to avoid confusion with system timestamps during reporting.

Jiva tags or category labels migrate to Monday CRM Tags or a dedicated Status/Dropdown column. Tags with no structural meaning in Monday CRM's model are migrated as Tags for filtering and grouping convenience. During migration, duplicate tags are merged automatically to prevent redundant entries in the target board.

Jiva workflow rules and enrollment triggers have no Monday CRM equivalent and must be rebuilt. We export the Jiva automation definitions as a structured document that your Monday CRM admin can use as a rebuild guide. Monday CRM's automation builder uses different trigger-action logic, so a direct translation is not possible.

Jiva reports and dashboards do not transfer to Monday CRM's widget-based dashboards. The underlying data (contacts, deals, activities) migrates in full, so you can rebuild equivalent charts and tables in Monday CRM's dashboard builder using the migrated data. All metrics remain accessible after the rebuild.