Migrate from mQuest to monday CRM

mQuest contacts map directly to monday CRM's People entity. Each contact record becomes a person item in the designated People board. Primary company association maps to a monday CRM Company connector column on the People board. Contact owner resolves by email match to a monday CRM user.

mQuest company records map to monday CRM's Companies board. Each company becomes an item with columns for name, domain, industry, employee count, and revenue. The company hierarchy (parent/child) maps to monday CRM's Group structure or a custom Link to Item column.

mQuest deals become items in monday CRM's Pipeline board (or a named equivalent board). The pipeline stages from mQuest map to monday CRM's Status column values. Each pipeline in mQuest corresponds to one monday CRM board. Deal values, close dates, and owners map to numeric, date, and person columns.

mQuest logged activities (calls, emails, meetings) migrate as items in a dedicated monday CRM Activity board, linked to the related contact or deal item via monday CRM's relation/connector columns. Original timestamps and activity type are preserved in custom columns. Each activity item also retains the owner information and any associated notes, ensuring that the full interaction history is accessible within monday CRM for reporting and follow-up.

Each mQuest custom field on Contact requires a new column in the monday CRM People board. FlitStack creates the column with the matching type (text, number, date, or dropdown) and maps values during migration. Dropdown fields use monday CRM's Status or Dropdown column type.

mQuest custom fields on Deals map to new columns in the Pipeline board. The column type is selected based on the source field's data type. For multi-select pick-lists in mQuest, FlitStack creates a monday CRM Tags column to preserve multiple selected values.

mQuest owner IDs resolve to monday CRM users by email address. Unresolved owners are flagged before migration — the team either invites the user to monday CRM first or assigns their records to a designated fallback owner. Owner resolution is logged in the migration audit trail.

Each mQuest deal pipeline stage name maps to a monday CRM Status column value on the corresponding Pipeline board. The mapping is defined one-to-one during planning. Stage order and color coding in monday CRM are applied based on the source stage sequence.

mQuest deal monetary amounts map directly to a monday CRM Numbers column. Currency is stored as a text note in the same column or a separate text column depending on whether multi-currency support is needed in monday CRM.

File attachments from mQuest records are downloaded and re-uploaded to the corresponding monday CRM item as file attachments. File size limits (default 250MB per file in monday CRM) are enforced. Inline images in notes are extracted and re-hosted as monday CRM image columns or file attachments. All attachments retain their original file names for simple identification.

If mQuest preserves stage-change timestamps, FlitStack creates a custom text or date column in the Pipeline board to store the historical stage transition log as a JSON string or multi-line text for audit continuity. This history column allows sales managers to review the full progression of a deal through pipeline stages, supporting compliance audits and performance analysis.