Migrate from Spark CRM to monday CRM

Spark CRM contacts migrate as items in a Monday CRM Contacts board. Each contact's standard properties (name, email, phone, job title, address) map to typed columns. Monday does not have a separate Lead object — Spark contacts with a 'Lead' status can either merge into the Contacts board or split into a separate Leads board depending on your preference.

Spark companies map as items in a Monday CRM Companies board. Monday does not enforce a primary-contact foreign key — each contact item links back to the company using Monday's relation column (relation type: boards) rather than a mandatory lookup field. Multi-contact companies require the relation column to be configured for one-to-many or many-to-many display.

Spark deals migrate as items in a Monday CRM Deals board. The deal name maps to the item name. Deal amount, close date, and owner map to number, date, and person columns respectively. Monday's status column replaces Spark's pipeline stage — we create one status column per Spark pipeline and map stage values to colored status labels. Stage probabilities do not carry over automatically and must be reconfigured in Monday reporting.

Spark pipelines do not have a direct Monday equivalent. Each Spark pipeline becomes a dedicated Deals board (or a separate group within one board) with its own status column. Stage names become status labels; stage order maps to the order of labels in the column configuration. Teams with multiple Spark pipelines should decide whether to consolidate into one Deals board with groups or keep separate boards per pipeline.

Spark's lead status pick-list values (New, Contacted, Qualified, Lost, Converted) map to Monday status labels on a dedicated Leads board. If you choose to merge leads into the Contacts board, a status column on that board serves the same purpose. Monday has no native lifecycle stage equivalent — any Spark lifecycle stage data must be stored as a separate label column or text column.

Spark owner assignments resolve by email match against Monday CRM workspace members. The matched user populates a person column on each item. Unmatched owners are flagged pre-migration — you either invite them to the Monday workspace first or assign records to a fallback person. Monday person columns store the workspace member, not the raw email address.

Spark activity records (calls, emails, meetings, notes) migrate as items in a Monday CRM Activity board. Each item carries type, date, owner, and content fields as typed columns. A relation column links activity items back to the originating contact item. Monday does not render a native activity timeline on the contact item — the Activity board serves as the history log. Original timestamps are preserved as date columns.

Spark file attachments on contacts, companies, or deals re-upload to Monday's file column on the corresponding board item. Monday file column stores up to 250 MB per file on Enterprise plans (10 MB on lower tiers). Inline images embedded in Spark notes are downloaded and reattached as Monday file items. Files that were shared via Spark links will not retain shareable URLs after migration.

Spark custom fields map to Monday custom columns by inferred data type: text fields become text columns, numbers become number columns, dates become date columns, and pick-lists become label columns. Monday's custom columns are board-scoped — a custom column created on the Contacts board does not exist on the Deals board. If the same custom field appears on multiple Spark objects, you need to create a matching column on each Monday board manually after migration.

Spark contact or deal tags migrate as Monday label column values or text column entries. Label columns are the preferred mapping because they support multi-select and color coding. If Spark uses a free-form tag model with no predefined vocabulary, a text column preserves the raw values without type enforcement.

Spark workflow rules — including lead-routing triggers, deal-stage automation, field-update rules, and notification actions — have no Monday CRM equivalent. Monday's automation recipes are board-scoped when-then triggers and cannot import Spark's conditional logic. We export your Spark automation definitions as a structured JSON reference document so your Monday admin can rebuild them in Monday's automation builder. Plan 2–4 hours per automation rule for the rebuild.

Spark CRM reports and dashboards are not portable. The underlying data (contacts, deals, activities) migrates, but the report configuration — chart types, filters, grouping, date ranges — must be recreated in Monday's dashboard builder. Monday dashboards aggregate from board items using widgets; chart variety is more limited than Spark's native report builder. Estimate 1–3 hours per report for the rebuild.