Atomic Object
How Atomic Object moved off Craft CMS and took ownership of their own website.
The problem
Atomic Object is a custom software development agency founded in Grand Rapids, Michigan. Their website ran on Craft CMS, and the team wanted a platform they could update and maintain themselves rather than routing every change through something that needed specialist attention.
For a company whose own business is building software, waiting on someone else to change a page is a particular kind of irritating.
The part that doesn't move on its own
Atomic Object publishes Spin, a blog that lives alongside the marketing site rather than inside it. A migration that moved the marketing pages and left Spin stranded would have solved half the problem and created a new one.
So the scope included wiring the two together with Zapier, so the blog and the new marketing site behave like one property from a reader's side.
The build
We migrated the site from Craft CMS to Webflow and built the integrations connecting Spin to the new marketing site.
The build is the easy half of a migration. The half that decides whether it was worth doing is whether the client's team can actually use what they have been handed.
What stood out to me the most about working with them was their dedication to the project. I predominantly worked with Hien and he was responsive, friendly, and broke down complex ideas and tasks in a way that helped me engage better with the project.
What they own now
After launch we ran one-on-one coaching and built a library of training videos for the Atomic Object team, so the people who publish could keep publishing without calling us.
That was the point of the move. A migration that ends with the client dependent on the agency has relocated the bottleneck rather than removed it.
Another one
