boxlang-cfml-migration

Migrate CFML codebases to BoxLang by mapping syntax and runtime behavior.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ortus-boxlang/skills --skill boxlang-cfml-migration-ortus-boxlang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: boxlang-cfml-migration
Source: https://github.com/ortus-boxlang/skills/tree/main/boxlang-developer/cfml-migration
Command: npx skills add https://github.com/ortus-boxlang/skills --skill boxlang-cfml-migration-ortus-boxlang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Moving CFML applications to BoxLang requires translating syntax, behavior, and runtime nuances to preserve functionality. This skill provides a structured methodology to map CFML constructs to BoxLang equivalents and coordinate compatibility work with bx-compat-cfml, reducing manual rewrite effort and risk.

Core Features & Use Cases

  • CFML-to-BoxLang syntax mapping for components, scripts, and templates, including file-type conversions and tag-prefix changes.
  • Compatibility guidance for runtime parity using the bx-compat-cfml module (client scope, cf_sql_ param syntax, date handling, and BIF renames).
  • Migration workflow guidance with step-by-step scenarios such as porting components, templates, and CFML-bridged code to BoxLang.

Quick Start

Begin by running the CFML migration workflow across your project to convert CFML types and syntax to BoxLang equivalents and enable bx-compat-cfml parity.

Frequently Asked Questions about boxlang-cfml-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate CFML codebases to BoxLang?

Migrate CFML codebases to BoxLang by mapping syntax and runtime behavior to BoxLang equivalents, converting .cfc/.cfm files to .bx formats, and enabling the bx-compat-cfml module to preserve functionality.

What CFML syntax changes are required when moving to BoxLang?

CFML migration to BoxLang requires replacing cfsqltype with sqltype, updating blockfactor to fetchSize, adjusting default scopes, aligning date handling, renaming BIFs, and updating template prefixes to ensure runtime parity.

Does the migration process support both Adobe CFML and Lucee code?

Yes, the CFML migration process applies to projects moving from both Adobe CFML and Lucee code, covering component, script, and template conversions while preserving functionality through compatibility mapping.

How does the bx-compat-cfml module maintain runtime parity during migration?

The bx-compat-cfml module enables runtime parity by handling compatibility for client scopes, cf_sql_ parameter syntax conversions, date handling alignment, and built-in function renames during the CFML to BoxLang migration.

Can I convert CFML templates and components to BoxLang formats automatically?

Yes, the migration workflow converts CFML templates and components by mapping file types like .cfc, .cfm, and .cfs to BoxLang formats like .bx, .bxs, and .bxm, while applying tag-prefix changes and syntax translation.