InkCMS Partners
Pre-vetted developers and agencies who specialize in InkCMS. Find the right partner for your project.
Read moreA fixed-scope service. We take your existing site — WordPress, Squarespace, custom — and stand it up cleanly on InkCMS. You keep your hosting, your domain, your team, your keys.
You've got a working site somewhere, and you'd like to be on InkCMS instead — for the editing experience, for the AI authoring, for the absence of plugin sprawl, for whatever reason brought you here. But you don't have the time (or want the time) to learn the platform from scratch and rebuild the site yourself.
This service is the bridge. We'll do the actual migration work — content extraction, template build, styling pass, hosting setup — and hand you back a clean InkCMS install that's ready to edit. Then we step out. You take it from there with your team, with a partner, or by yourself.
We extract your pages, posts, images, and media from your current CMS and reshape them into InkCMS's filesystem layout — Markdown + frontmatter, organized into the directory structure that matches your site's URLs.
Sources we handle: WordPress, Drupal, Squarespace, Webflow, Ghost, custom CMSs, raw HTML.
Old sites accumulate cruft. We tighten copy, fix broken links, audit metadata + redirects, normalize image sizes, and rewrite anything that didn't survive the migration cleanly. Plus we set up the AI authoring layer with brand voice + prompts tuned to your site.
No copy changes you didn't ask for.
Two paths. Carry-over: we replicate your current look as InkCMS Razor templates + CSS so the site doesn't visually change on launch day. Refresh: we update the design at the same time — type system, color, spacing, modern responsive patterns. You pick which.
Refresh path adds 1–2 weeks.
We walk you through standing up the InkCMS install on your hosting. Azure App Service, IIS, Linux + Kestrel — we configure it on your account, with your credentials, alongside someone from your team. Then we deploy + cut DNS at launch.
DNS cutover is staged — you can roll back.
This is the part most agencies get wrong. We don't run your site after the migration. The hosting account is in your name and on your credit card. The domain registration is in your name. The SSL certificate is in your name. The InkCMS license is in your name.
If you fire us mid-engagement, you walk away with everything we've built up to that point. If you fire us after launch, you walk away with a working site running on your own hosting.
A note on timeline + scope.
Every migration is different. A small brochure site with no integrations runs on the short end of the range. A content-heavy site with custom forms, third-party integrations, and a styling refresh runs on the long end. Sites with unusual constraints — bespoke CMSs, hand-built integrations, large media libraries, multi-language — take longer still.
We won't commit to a calendar window until we've reviewed your existing site. The discovery call gives us enough to put a real scope + timeline in writing — and we hit the dates we commit to.
Migrations vary too much to publish a price list — content volume, integrations, design refresh vs. carry-over, hosting target. We look at the existing site during discovery, ask the questions that matter, and send back a written scope + price.
What you get in the quote: a clear scope statement, a fixed price for that scope, a target timeline, and the assumptions we made to arrive at both. If scope shifts mid-engagement, we send a written revision before doing the work — no surprise change orders, no hourly creep.
What's separate from our quote: your InkCMS license (separate, on your account) and your hosting (separate, on your account). We don't bundle them or mark them up; you pay InkCMS directly and you pay your hosting provider directly.
URLs, rough page count, current CMS, anything weird about the integrations. We'll send back a written scope + quote within 48 hours.