Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows.
Install the "migrate-k2-nintex" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/migrate-k2-nintex into .claude/skills/migrate-k2-nintex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-k2-nintex", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add mendixlabs/mxcli --skill migrate-k2-nintex -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "migrate-k2-nintex" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/migrate-k2-nintex into .agents/skills/migrate-k2-nintex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-k2-nintex", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add mendixlabs/mxcli --skill migrate-k2-nintex -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "migrate-k2-nintex" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/migrate-k2-nintex into .cursor/skills/migrate-k2-nintex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-k2-nintex", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add mendixlabs/mxcli --skill migrate-k2-nintex -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "migrate-k2-nintex" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/migrate-k2-nintex into .gemini/skills/migrate-k2-nintex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-k2-nintex", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add mendixlabs/mxcli --skill migrate-k2-nintex -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "migrate-k2-nintex" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/migrate-k2-nintex into .github/skills/migrate-k2-nintex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-k2-nintex", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add mendixlabs/mxcli --skill migrate-k2-nintex -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "migrate-k2-nintex" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/migrate-k2-nintex into .opencode/skills/migrate-k2-nintex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-k2-nintex", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
migrate-k2-nintex
GitHub stars
128
Token cost
~4.1k tokens
SKILL.md length
1,161 words
Files
1
Skills in repo
72
Repo updated
First seen
Licence
Apache-2.0
At a glance
Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows.
Works in 11 steps: K2 Package (.kspx) → Legacy Project Files → K2 APIs → …
Converting a K2 application
SKILL.md covers When to Use This Skill, Understanding K2 Application…, Export and Package Options and Migration Strategy, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Migrate K2 Nintex is an agent skill from mendixlabs/mxcli. Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows. Use when analysing or converting a K2 application.
Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office. It works with Microsoft SharePoint. The repository describes itself as: Mendix cli tool, a headless way to work with Mendix projects. Enables Mendix projects for use with 3rd party agentic coding tools like Claude Code and Copilot. Includes a… The licence is Apache-2.0.
When your agent uses it
Converting a K2 application
Example prompts
“/migrate-k2-nintex”
Workflow steps
11 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 20a6c89. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are sql, markdown and csharp).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Migrate K2 Nintex loads about 4.1k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 1,161 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~57
When it runs· the whole SKILL.md, loaded when a task matches
~4.1k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/migrate-k2-nintex/SKILL.md (or your agent's skills folder).
name
migrate-k2-nintex
description
Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows. Use when analysing or converting a K2 application.
K2/Nintex to Mendix Migration Skill
This skill provides comprehensive guidance for assessing and migrating K2 (now Nintex K2) applications to Mendix using MDL (Mendix Definition Language).
When to Use This Skill
Use this skill when:
Analyzing K2/Nintex applications for migration to Mendix
Converting SmartObjects to Mendix domain models
Mapping SmartForms Views to Mendix pages
Translating K2 Workflows to Mendix microflows or workflows
Planning a migration strategy for legacy K2 systems
Understanding K2 Application Architecture
K2 applications are fundamentally different from Mendix in how they're stored and structured.
K2 Storage Model
Key Difference: K2 applications are server-side/database-stored, not file-based like Mendix. All K2 project elements and data are saved into the K2 database, not as files. This is one of the key challenges for migration.
Aspect
K2/Nintex
Mendix
Storage
Server database
.mpr file (SQLite)
Versioning
Server-managed
Git-based (MPR v2)
Export format
.kspx package
.mpk package
Project file
No single file
.mpr project file
K2 Artifact Types
A K2 application is composed of several artifact types:
SmartObjects
Middle layer between data providers (SQL, SAP, SharePoint) and data consumers (forms, workflows, reports). They abstract data from LOB systems.
SmartObject Type
Description
Mendix Mapping
SmartBox
Stores data in K2's own database
Persistable Entity
SQL Connector
Connects to SQL Server tables
External Database Connector
SAP Connector
Connects to SAP systems
OData/REST Integration
SharePoint Connector
Connects to SharePoint lists
REST Client
Service Object
Exposes services/methods
Microflow/Java Action
SmartForms
Browser-based forms composed of Views and Forms:
SmartForms Element
Description
Mendix Mapping
View
Reusable collection of controls + rules bound to SmartObjects
Process definitions with steps, tasks, branching logic:
Workflow Element
Description
Mendix Mapping
Workflow
Full process definition
Workflow or Microflow chain
Activity
Individual step in workflow
Microflow activity or User Task
Task
Human task requiring user action
User Task
Destination Rule
Routing logic for tasks
Decision (microflow)
Datafield
Workflow data variable
Parameter or Variable
Export and Package Options
There's no single "project file" like Mendix's .mpr. Your options for extracting K2 app definitions:
1. K2 Package (.kspx)
The K2 Package and Deployment tool packages K2 artifacts (SmartObjects, forms, views, workflows) into a single file with a .kspx extension. This is the primary mechanism for moving apps between environments.
How to export:
K2 Management Site → Solutions → Package → export
2. Legacy Project Files
Older K2 Studio / K2 for Visual Studio projects used:
File Type
Extension
Contents
Project file
.k2proj
Project structure and references
Workflow definition
.kprx
Workflow definition
SmartObject definition
.sodx
SmartObject schema
3. K2 APIs
SmartObject Runtime API and management APIs can be used programmatically to extract definitions:
csharp
// Example: Programmatic SmartObject extraction
using SourceCode.SmartObjects.Client;
SmartObjectClientServer server = new SmartObjectClientServer();
server.CreateConnection();
SmartObject so = server.GetSmartObject("CustomerSO");
// Extract properties, methods, etc.
Migration Strategy
For a K2 → Mendix migration, approach it in layers:
Layer 1: Data Model (SmartObjects → Entities)
SmartObject Type
Migration Approach
SmartBox SmartObjects
Direct translation to Mendix persistable entities
SQL Connector SmartObjects
Options: (a) Import data to Mendix, (b) External Database Connector
SmartForms Views map to Mendix pages/snippets. The rules system (event-driven, "when X happens, do Y") maps well to Mendix's nanoflow/microflow-on-events pattern.
mdl 1;
-- Module roles matching K2 roles
create module role CRM.Manager description 'Can approve orders and manage customers';
create module role CRM.User description 'Can create and edit own records';
-- Access rules
grant create, delete, read *, write * on entity CRM.Order to CRM.Manager;
grant create, read *, write * on entity CRM.Order to CRM.User where [System.owner = '[%CurrentUser%]'];
Common Challenges and Solutions
Challenge 1: Server-Side Storage
Problem: K2 stores everything in a database, no single project file.
Solution: Use K2 Package (.kspx) export or K2 APIs to extract definitions. Work with K2 administrators to get comprehensive exports.
Challenge 2: SmartObject Connectors
Problem: SmartObjects may connect to external systems (SQL, SAP, SharePoint).
Solutions:
Connector Type
Mendix Options
SQL Direct
External Database Connector or data migration
SAP
SAP BAPI Connector, OData, or REST
SharePoint
REST integration via Microsoft Graph API
Web Service
REST/SOAP consumption
Challenge 3: Complex Rules
Problem: SmartForms rules are event-driven and can be deeply nested.
Solution: Map each rule to appropriate Mendix mechanism:
Migrate K2 Nintex next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Distill a colleague into a reusable AI skill (work + persona) using tool connections — Slack, Slack AI, Jira, GHE, Bitbucket, Confluence, SharePoint, Teams, Outlook, Notion, Linear, Google Docs, and…
Work with Microsoft 365 services via the Graph API — emails, calendar events, SharePoint sites (read and write), Teams chats and channel messages, OneDrive files, OneNote notebooks, Planner task…
Guides work with Outlook, OneDrive, SharePoint, Teams, Excel, To Do and Planner through aai-cli's Microsoft Graph commands, starting from which service owns the data.
Analyze the current SharePoint document library in read-only mode and produce a structured summary of files, folders, file types, recent activity, naming issues, and organization recommendations.
Push OData query options into the SQL of a Mendix resource served by a read microflow, so $filter, $orderby, $top, $skip, $count and the key lookup reach the database instead of being silently…
Chart a Mendix app with Vega-Lite through a pluggable widget that takes the specification and the data as separate properties, so the model emits rows and never assembles a chart payload.
Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows. Migrate K2 Nintex is an agent skill from mendixlabs/mxcli. Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows.
When should I use Migrate K2 Nintex?
Migrate K2 Nintex fits situations like: converting a K2 application.
How do I install Migrate K2 Nintex in Claude Code?
Run `npx skills add mendixlabs/mxcli --skill migrate-k2-nintex -a claude-code`. Or copy the skill folder (.claude/skills/mendix/migrate-k2-nintex in mendixlabs/mxcli) into .claude/skills/migrate-k2-nintex in your project. Claude Code loads it when a task matches its description.
How do I install Migrate K2 Nintex in Codex?
Run `npx skills add mendixlabs/mxcli --skill migrate-k2-nintex -a codex`. Or copy the skill folder (.claude/skills/mendix/migrate-k2-nintex in mendixlabs/mxcli) into .agents/skills/migrate-k2-nintex in your project. Codex loads it when a task matches its description.
Can I use Migrate K2 Nintex in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mendixlabs/mxcli --skill migrate-k2-nintex -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/migrate-k2-nintex, .gemini/skills/migrate-k2-nintex, .github/skills/migrate-k2-nintex and .opencode/skills/migrate-k2-nintex in your project.
What does Migrate K2 Nintex need to run?
SKILL.md names no scripts, command-line tools or credentials: Migrate K2 Nintex is instructions for the agent only.
Does Migrate K2 Nintex access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Migrate K2 Nintex safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Migrate K2 Nintex use?
Migrate K2 Nintex is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Migrate K2 Nintex use?
About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Migrate K2 Nintex?
Skills that share tags, products or a category with Migrate K2 Nintex: Colleague Distillation (ZhixiangLuo/10xProductivity, 478 stars), Msgraph (codemie-ai/codemie-code, 294 stars), aai-cli Microsoft 365 (aai-labs/agent-barn, 109 stars) and Workiq (microsoft/work-iq, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Migrate K2 Nintex?
mendixlabs (a GitHub organization) maintains it in mendixlabs/mxcli, which has 128 GitHub stars. The repository holds 72 skills in this directory. The repository was last updated on October 7, 2026.
Source: mendixlabs/mxcli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.