Migrate from ContactDB to monday CRM

ContactDB contact records map to Monday.com CRM contact items in the Contacts board. Standard contact fields (Name, Email, Phone, Job Title) map to Monday's built-in name, email, phone, and text columns. ContactDB firmographic signals including SICCODE, credit rating, company size, and industry are mapped to custom columns in the Contacts board. Since Monday.com does not have a native lifetime value or lead quality field, these values are stored as numeric or dropdown custom columns if the customer specifies them during scoping.

ContactDB exposes company name, industry, size, and SICCODE per contact as attributes rather than standalone company records. We extract unique company values across all contact records, deduplicate by company name, and create a Companies board entry for each unique company. The Contacts board item is then linked to the Companies board item via Monday.com's Board Relations column. This resolves the one-to-many relationship where multiple ContactDB contacts reference the same company.

ContactDB segments contacts by industry, profession, title, country, and software-usage criteria, but these segment labels are not exported as standalone tag objects. We reconstruct segment membership as Monday.com multi-select columns on the Contacts board, one column per segment category. The customer confirms which segment categories are meaningful post-migration during scoping. This requires the Contacts board to have the segment columns created before import so that values map directly during the API load.

ContactDB stores no engagement or activity data. Monday.com CRM does not have a native engagement timeline equivalent to HubSpot's activity log, but tasks can be created as items in a separate Activity board and linked to contact records via Board Relations or the connect board feature. We configure this structure during migration and advise the customer on the post-migration workflow for logging outreach activity against imported contacts. Any warmth or engagement signals must originate from the customer's outreach tools after migration, not from ContactDB.

ContactDB does not implement a deal or pipeline model natively. However, some customers using ContactDB for B2B outreach track deal potential externally or in spreadsheets alongside their purchased lists. If Deal records are in scope, we map them to Monday.com board items with a Status column representing pipeline stages (Prospecting, Qualified, Proposal, Won, Lost), a Value column for deal amount, and Board Relations linking each Deal item to the associated Contact and Company items.

ContactDB does not export tag objects as standalone entities. Segment criteria (industry, profession, title, country, software usage) are the closest equivalent and are handled through the multi-select segment columns described above. If the customer has internal tag annotations that were added post-purchase, those are captured as a free-text Notes column on the contact item, since Monday.com does not have a native tags object at the contact level in the CRM module.

ContactDB does not document a custom fields schema. Any extended attributes stored against contacts in ContactDB are proprietary to the platform and not exposed in export packages. If the customer has supplementary data they added manually (internal IDs, campaign codes, custom scores), these must be disclosed during scoping so we can map them to Monday.com custom columns of the appropriate type (text, number, date, dropdown) before import begins.

ContactDB is a data product with no internal user accounts, so there are no Owner assignments in the source data to migrate. In Monday.com CRM, contact items can be assigned to team members for accountability. We configure a Team Members column on the Contacts board during migration and leave assignments open for the customer's admin to set post-migration based on territory or campaign ownership.