iModules to WordPress Migration
Encompass, formerly iModules, changed owners in 2026. Move your alumni and advancement site to WordPress, with your stories, URLs and units accounted for, and your giving, events and CRM connected the way you choose.
The real problem
The site publishes, the giving forms take gifts and the events fill up. What slows you down is that every page lives inside a suite, and the suite’s direction is set by whoever owns it.
Anthology filed for Chapter 11 in September 2025, and Encoura says it has owned Encompass since 2 February 2026. A new owner sets a new roadmap. It is a good moment to decide where your site should live for the next campaign.
Still weighing the platforms? Compare WordPress and iModules.
What the migration covers
A migration is not a content export. These are the six layers that decide whether the new site behaves like the old one on launch day.
Content mapping
Alumni stories, news, campaign and event pages are inventoried and mapped to WordPress post types, fields and taxonomies, so each piece lands where your editors expect it.
Templates and brand
Suite templates become blocks and patterns built on your university’s design system, so the advancement site looks like the rest of the institution.
Media and documents
Images and documents import with duplicates removed. A second pass rewrites every reference in the content, so nothing breaks after launch.
URLs and redirects
Every URL search engines and past emails link to is captured with a full crawl, plus analytics and Search Console. The redirect map is built from that crawl, and one rule holds: no redirect chains.
Giving, events, email and CRM
Each one is reviewed in the diagnosis and sorted: stays on its current tool and links from the site, moves to the tool you choose, or connects to WordPress. Each connection is tested before the switch.
Units, users and roles
Schools, colleges and units come across with their own sections. Users map onto WordPress roles, so each unit edits its own pages.
What changes
After the migration, the people who write the stories are the people who publish them.
Editors assemble pages from approved blocks on the university’s design system and see the result as they work. Giving, events and email run on the tools you chose, and changing one no longer means replacing the site.
Not iModules, but the same problem: Northeastern University School of Law’s campaigns waited on engineering until 40Q rebuilt its UI framework as a WordPress theme, and today the communications team launches on-brand pages on its own. Read the case
The plan
Three steps, with a decision point at the end of each one. Your Encompass site stays live until the new one is verified.
A full crawl of your site, a content inventory, a review of giving, events, email and CRM, and a baseline of every URL, canonical tag and metadata value. Then a pilot: a real slice of content migrated end to end, so the mapping is proven before the full run.
Frontend, backend and content migration run in parallel while Encompass stays live. QA covers browsers, giving and event connections, and the editor workflows, tested with the people who will use the CMS.
Cutover with the previous site kept available, so rollback is a decision rather than a project. We watch rankings and coverage until they settle, and keep improving the platform with your team.
Before you commit
In 30 minutes we look at your site, your giving and event pages and your CRM connection, and tell you what moving involves and what can stay. No commitment.
FAQ
The questions teams ask before they decide, answered plainly.
Ready when you are
Bring us your iModules site and we will map the path off it: stories, redirects, giving, events, units, and the workflows your team will use on day one.
