Migrate from cMercury to monday CRM

cMercury Subscriber records map to Monday.com People as individual contacts. Email address, subscription status, and all custom profile fields migrate as typed Monday.com columns. The cMercury subscription status (active, unsubscribed, bounced) becomes a status column in Monday.com People. Any cMercury custom field (text, number, date, dropdown) maps to the equivalent Monday.com column type. We resolve duplicates using email as the dedupe key and flag conflicts for the customer's admin to resolve before final import.

cMercury Tags are flat labels applied to Subscribers. We export all tag names and their per-subscriber assignments and recreate them as Monday.com Labels on the People entity. Labels in Monday.com appear as colored tags on contact records and can be used to filter People Views. Tag count and naming are preserved verbatim.

cMercury Segments are defined by filter rules on engagement, custom field values, and source. We extract the full segment rule tree and translate it into a Monday.com People filtered View with equivalent conditions. Complex nested conditions (AND/OR logic with multiple levels) may require simplification or multiple Views; we document these as part of the handoff and flag any segment that cannot map directly to Monday.com's filter UI.

cMercury Campaign records include subject, content, send date, and aggregate performance stats (opens, clicks, bounces). Monday.com has no native campaign object, so we create a Campaign Board with Items representing each cMercury campaign, with performance stats stored as custom columns. Campaign content (HTML body) migrates as a text column or attachment. Because Monday.com cannot send email natively, campaign-level metrics serve as historical reference rather than active campaign tracking.

cMercury custom fields on Subscribers (text, number, date, dropdown, checkbox) map directly to Monday.com column types: Text to Text, numbers to Numbers, dates to Date, dropdowns to Dropdown or Labels, and checkboxes to Checkbox. Data type fidelity is preserved. If the destination Monday.com workspace uses a separate People board for contacts, custom fields that apply to all contacts go on the People board; fields specific to a campaign context go on the Campaign board.

cMercury tracks a per-subscriber engagement score (numeric value). We export the score value and map it to a Numbers column on the Monday.com People entity. The column is labeled Engagement Score in the destination. If the score is derived from multiple factors, we store it as a read-only reference value; recalculation logic does not migrate because Monday.com does not have an equivalent scoring formula engine.

cMercury Verify stores per-email validation status (valid, invalid, risky, catch-all). We preserve this as a status column on the Monday.com People record, with the badge value as the status label. This allows the customer's team to see verification quality at a glance in Monday.com without needing to re-verify in the new system. Invalid addresses are flagged in the import report for the admin to review.

cMercury email templates use a proprietary block structure. We extract the HTML from each template and save it as an HTML file attached to a Monday.com Board or Item. Template layout may not render identically in Monday.com because Monday.com does not have an email template editor. We note which templates should be rebuilt in the customer's chosen email marketing platform post-migration.

Images and files stored in cMercury's Asset Library are downloaded with their original file names and uploaded to Monday.com Files attached to the relevant Board. Folder organization is preserved where the destination supports folder structure. Large asset libraries may require bulk upload via Monday.com's file upload API with chunking for files over 5 MB.

cMercury Automations are trigger-action sequences tied to subscriber behavior (subscribe, open, click, tag applied). Monday.com Automations are board-level triggers for task status changes, notifications, and column updates. These are fundamentally different automation models with no meaningful translation. We document every cMercury Automation's trigger conditions, conditions, and action sequence in a written inventory for the customer's admin to evaluate rebuilding in Monday.com Automations (Pro plan required). Expect 1-2 hours of rebuild time per automation.

cMercury sending domains are configured with DKIM, SPF, and DMARC records tied to cMercury's mail infrastructure. These cannot be transferred to Monday.com because Monday.com does not have a native email sending layer. We provide a DNS checklist during cutover specifying which records to remove from cMercury and which records to add for the customer's new email sending platform (Mailchimp, Klaviyo, or equivalent). Deliverability history does not transfer.