Migrate from Spiro to monday CRM

Spiro Company records map to Monday.com CRM Organizations, which are built on a dedicated CRM board. We extract company name, address fields, domain, and any custom Company fields from Spiro's schema (confirmed via CSM before migration) and map them to Organization name, location columns, and custom columns on the CRM board. If Spiro stores multiple addresses per Company, we preserve the primary address and add secondary addresses as subitems or multi-line text columns.

Spiro Contacts migrate to Monday.com CRM Contacts on the same CRM board as Organizations. Standard fields (name, email, phone, title, company link) map directly. Custom Contact fields from Spiro (confirmed via CSM) are recreated as Monday.com column types: text fields, date columns, dropdown selects, or checkbox columns depending on the source data type. Contact-Organization linking is preserved via Monday.com's people column or a reference column pointing to the Organization item.

Spiro Opportunities map to Monday.com CRM Deals. Deal value maps to a number column, close date to a date column, and stage to a status column. Spiro stage names are reconciled against Monday.com status column values during scoping — if the destination has no matching status label, we create one or map to the closest equivalent and flag the discrepancy. Owner assignment maps to the Monday.com team member assigned to the Deal item.

Spiro custom field definitions must be obtained from Spiro's CSM or extracted from the UI because there is no self-service API endpoint for the schema. We recreate each custom field as a Monday.com column type before importing data. Supported column types include text, numbers, date, dropdown, checkbox, email, phone, URL, location, and rating. Complex Spiro picklists become Monday.com dropdown columns with values migrated verbatim.

Monday.com CRM does not have a native activity log object. We store email history as subitems under the relevant Contact or Organization item, using a subitem type column, date column, notes column, and a person column for the owner. Email body content migrates as a long-text note. Alternatively, for high-volume activity histories, we create a separate Activity board and link each activity subitem to the Contact or Organization via an connect boards column.

Call records from Spiro (disposition, duration, notes) migrate as subitems under Contact or Organization using a subitem type column set to 'Call', a date column for the call timestamp, a number column for duration, and a notes column for disposition and content. Owner is assigned via the person column. This approach preserves the chronological activity timeline within the Monday.com board structure.

Meeting records migrate as subitems with a meeting type marker, start and end datetime columns, a location text column, and attendee information stored as a people column or free-text note. We preserve the meeting title in the subitem name field. If the Spiro meeting includes notes or outcome text, this migrates as a notes column.

Spiro Notes linked to Contacts or Companies migrate as subitems with a note type marker, a date column for the creation timestamp, and the note body as a long-text notes column. We attach the original note author via the person column. If the note references any files, those attachment URLs are flagged for re-linking in Monday.com.

Spiro user records map to Monday.com workspace members. We match by email address and assign the corresponding Monday.com member to Contact, Organization, Deal, and Activity items. Any Spiro Owner without a matching Monday.com user is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Spiro users are mapped to inactive Monday.com members with activity records flagged for reassignment.

Spiro Opportunity stage names map to Monday.com status column values on the Deals board. During scoping, we collect all distinct Spiro stage names and create matching Monday.com status options. Spiro stage probability values are not natively supported in Monday.com's status column; if the customer requires stage probabilities for forecasting, we document this gap and recommend a number column to track probability or a reporting-level workaround.

Spiro stores attachments as linked URLs rather than embedded files. We verify each URL is reachable before migration and re-link them in Monday.com either as a URL column pointing to the original source (if the source remains accessible) or by downloading and re-uploading the file to Monday.com native storage (converting the link to a Monday.com-hosted file). If the Spiro workspace is revoked post-migration, any attachment links that were not re-uploaded become orphaned.

Spiro tags on Contacts and Companies map to Monday.com tags on the corresponding items. Tags are preserved verbatim. If the same tag appears across multiple record types in Spiro, we apply it consistently to the migrated Monday.com items.