Migrate from Giva eHelpDesk to monday CRM

Giva tickets map to Monday items on a dedicated support board. Each ticket ID becomes the Monday item's Name or a custom ID column. Original ticket status (New, Open, Pending, Resolved, Closed) maps to Monday status labels. Priority (Low, Medium, High, Critical) becomes a Monday priority column or status color coding.

Giva end-user contact records (name, email, phone, company) migrate as Monday CRM Contacts. Email serves as the unique identifier for deduplication. If a Giva end user has no email, FlitStack generates a placeholder identifier and flags the record for manual review before the full migration runs.

Giva ticket categories (e.g., Hardware, Software, Billing) map to Monday board groups. Each unique Giva category becomes a group header on the support board. Items auto-sort into groups based on a Category column value during migration so the board layout matches Giva's folder structure.

Giva agents resolve to Monday workspace members by email match. FlitStack inventories Giva agent emails against Monday user list before migration. Unmatched agents receive a fallback assignee (typically the board admin) and the original agent is stored in a custom column for audit purposes.

Giva priority levels (Critical, High, Medium, Low) map to Monday label columns with color coding (red for Critical, orange for High, yellow for Medium, green for Low). The value-by-value mapping is created as a Monday labels column so teams can filter by priority directly on the board view.

Giva status values (New, Open, Pending, On Hold, Resolved, Closed) map directly to Monday status column options, preserving the original workflow stages on the board. FlitStack stores each status‑change timestamp in a separate DateTime column, allowing historical SLA calculations to continue in Monday's time‑tracking setup and supporting accurate reporting of resolution cycles after migration.

Giva knowledge-base articles have no direct Monday CRM equivalent. FlitStack exports article titles, body content, and categories as a structured JSON package. Your team rebuilds these as monday Docs or links them from the support board via a URL column. The export file serves as the rebuild reference.

Giva asset records (asset tag, type, serial number, assigned user, location) migrate as items on a separate Asset Board in Monday. Each asset links to its assigned contact via Monday's connect boards column so support tickets can reference the relevant asset without duplicating data.

Giva email templates are platform-specific HTML constructs with merge fields. Monday CRM does not have a native email-template library for ticket responses. FlitStack exports template names and body content as a text file. Your team recreates them in Monday's email integration settings or a connected email tool.

Giva custom fields on tickets (e.g., Contract Type, Billing Account, Region) become Monday custom columns on the support board. FlitStack maps field type to the closest Monday column type: text fields become text columns, pick-lists become labels or dropdowns, dates become date columns, and numeric fields become number columns with formatting.

Giva file attachments on tickets download and re-upload to Monday items via Monday's file API. Files attach to the corresponding item using the original filename and timestamp. Monday's 250 MB per-file limit (Pro/Enterprise) accommodates most support attachments; files exceeding this threshold are flagged and linked by URL instead.

Giva SLA policies define response and resolution windows per category or priority. Monday CRM has no native SLA enforcement engine. FlitStack exports SLA policy names and thresholds as a configuration reference. Your team implements SLA tracking using Monday's deadline columns and automation recipes that trigger reminders at SLA breach points.