Migrate from Moskit to monday CRM

Moskit Contact records map to Monday.com CRM People entities. The Person's name, email, phone, and custom properties migrate to the People entity fields. We run schema-discovery on Moskit's Contact object first to enumerate all active custom fields, then configure equivalent People custom fields in Monday.com before import. Brazilian Portuguese field labels (Nome, Email, Telefone) are preserved in the data but flagged in a translation glossary so the Monday.com admin can rename columns post-migration.

Moskit Empresa records map to Monday.com CRM Organization entities. The organization's name, domain, address, and custom properties migrate to the Organization. We resolve the contact-to-company linkage by querying Moskit's contact-company relationship table and then setting the Person's organization reference during Monday.com import. If a contact has no linked company in Moskit, the Person is created without an organization reference.

Moskit Deal records map to Monday.com CRM Deal entities. The deal's name, value, stage, owner, expected close date, and custom properties migrate to the Deal. Moskit's pipeline stage names map to Monday.com Deal status columns (Negotiation, Proposal Sent, Won, Lost). We configure the destination Deal board columns before migration so that stage values are available as valid options at import time.

Moskit pipeline stages (custom-named, with stage-order sequencing) map to Monday.com Deal status column options. Stage-level win/loss probability from Moskit migrates as a numeric custom column in Monday.com Deal entities if the customer requires probability tracking. We note that Monday.com Deal entities do not have a native probability field; the customer decides whether to add a custom number column for this.

Moskit Activity records (tasks, calls, meetings, notes) linked to Deals or Contacts migrate as Updates on the corresponding Monday.com CRM Deal or People entity. Activity type (call, meeting, task, note) migrates as a label within the Update text. Timestamps and owner assignments are preserved in the Update metadata. We cannot replicate Moskit's native activity timeline UI; the Update log serves as the historical record in Monday.com.

Moskit Projects (deal-spawned with tasks, dates, and assignments) map to Monday.com Boards. Project name, description, and due dates migrate as Board metadata. Tasks within the Moskit Project map to Board Items. The critical mapping challenge is preserving the deal-to-project linkage: we run a two-pass import where Deals are imported first and their destination IDs captured, then Projects are imported with the deal reference remapped to the destination Deal IDs. If Projects are imported before Deals, that linkage breaks silently.

Moskit custom fields on Contacts, Companies, Deals, and Activities map to Monday.com board columns. Field types are matched: text fields to Text columns, numbers to Number columns, dates to Date columns, picklists to Status or Dropdown columns, and multi-select picklists to multi-select Status columns. Boolean fields map to Checkbox columns. We query each Moskit object type individually (Contacts, Companies, Deals, Activities) during schema discovery because Moskit does not expose a single endpoint enumerating all custom field definitions.

Moskit User records (name, email, role) map to Monday.com team members. We extract every distinct owner referenced on Contact, Company, Deal, and Activity records and match by email against the Monday.com destination workspace. Users without a matching Monday.com account go to a reconciliation queue for the admin to provision before record import resumes. Inactive Moskit users are included with a deactivation flag.