Stop rebuilding Magento CMS pages across environments.
Push and pull pages and blocks, with their images, between staging, pre-production and production. Preview and compare before anything goes live, and restore any earlier version.
Interest list only · one email to confirm · unsubscribe anytime · privacy
Founding members get [PLACEHOLDER: founding offer, to be approved] · or book a 30-minute walkthrough
- cms_page / homeedited
- cms_block / footer
- cms_page / homereceived
- cms_block / footer
- cms_page / homeedited 5 min ago
- pull the latest first↑
Built by Foxycom, the Adobe Commerce engineering team behind it
Adobe Solution & Technology Partner
Foxycom is an Adobe partner on both programmes.
Trusted by Les Mills
Ongoing Adobe Commerce support for the global fitness brand.
Meet Magento Poland 2026
Miloš on scaling Magento to a billion B2B prices.
100% in-house, Belgrade
Senior engineers. No outsourcing, no rotating teams.
- Push
- Pull
- Images come along
- Store view mapping
- Conflict detection
- Code comparison
- Visual comparison
- Preview in your theme
- Revision on every save
- Trash and restore
- Undo
- Export and import
- Magento Open Source
- Adobe Commerce
Page Builder pages don't copy. They get rebuilt, block by block.
By hand in Page Builder, every release
- 01Open the page in Page Builder on staging, next to production
- 02Drag every row, column and content block back into place
- 03Re-enter text, links and each element’s settings, desktop and mobile
- 04Download every image, upload it again, reselect it in each element
- 05Rebuild embedded blocks and widgets, and pick their IDs again
- 06Set the store view, then compare both pages by eye
- 07Hope nobody edited production in the meantime
With CMS Harmony
- 01Pick the pages or blocks.
- 02Review the code and visual comparison.
- 03Push. The page goes as built, with its images and embedded blocks.
What rebuilding by hand costs you. In your own numbers.
Every Page Builder page that moves between environments by hand is somebody's paid time. Move the sliders to match your team and see what it adds up to in a year.
Your numbers
Count each page or block once, however many edits it had.
Dragging the layout back, content, images, settings, checking.
Every store view or language version is rebuilt on its own.
Production only is 1. Add one for pre-production.
Developer or content editor, fully loaded.
Rebuilding by hand, your team spends
40hours a year
That's €1,800 of paid team time, every year, spent on work the module does for you.
1 of 52 full work weeks a year, rebuilding pages that already exist.
120
page moves a year
5
working days
€15
per page, store view and environment
Calculated only from the numbers you entered. It is not a measurement of CMS Harmony.
And that's before anything goes wrong
A missing image
One forgotten upload and production shows a broken banner.
Images travel with the content.
The wrong store view
The page lands in the default store instead of the right one.
Store views are mapped between installations.
A broken block reference
An embedded block points at an ID that means something else on production.
Embedded blocks go with the page, references rewritten.
A setting that didn’t make it
Padding, alignment or mobile visibility lost somewhere in the rebuild.
The page goes as built. Nothing is rebuilt.
Someone else’s edit, overwritten
Production changed while you were rebuilding staging’s version.
Conflict detection flags it before the push.
Push a block. Images included.
Walk through a push the way it works in the module: compare, decide what happens to each image, confirm. Then turn on the conflict and see what happens when production changed first.
Staging
- cms_page / home
- promo · changed
- cms_block / footer
Media
- banner-autumn.jpgnew
- hero.jpgv2
- truck-icon.svg
Production
- cms_page / home
- promo
- cms_block / footer
Media
- hero.jpgv1
- truck-icon.svg
- old-banner.jpg
Staging has a new delivery message and a new autumn banner in the promo block. Production still shows the old version.
A simplified simulation of the workflow, not the product interface.
Review before it's live. Recover when it isn't.
Compare before it goes live
Read the change as code, line by line, or let CMS Harmony render both versions and point at the parts of the page that look different.
- 01Pick the page or block on both sides.
- 02Read the code comparison.
- 03Check the visual comparison of the rendered pages.
Preview in your real theme
See a page or block the way visitors will, before you pull or push it, including how it will look on the destination.
- 01Open a signed preview link.
- 02Check it in context, a block inside the page it lives on.
- 03Publish the staged version, or discard it.
Every save becomes a revision
Each page and block save keeps a revision with its images. Restoring one backs up the current version first, and a draft is simply a revision you haven’t published.
- 01Edit and save as usual.
- 02Find any earlier version in the page’s history.
- 03Restore it, or undo a push or pull.
cms_page / home · history
- today, 14:02 · youHero text changedcurrent
- today, 11:40Pulled from productionRestore
- yesterday · editorDraft saved, not publishedPublish
- 3 days ago · editorNew banner imageRestore this one
Deleted isn’t gone
Deleted pages and blocks go to trash with their whole history and come back with it. Images that other content still uses are never removed.
- 01Delete a page or block as usual.
- 02Find it in trash with its revisions.
- 03Restore it, or delete it for good.
trash
Move content without a connection
Export selected pages and blocks into one archive with their images, and import it on another installation with store mapping and a dry-run report first.
- 01Select what to export, with or without revisions.
- 02Upload the archive and map store views.
- 03Read the dry-run report, choose what happens on conflicts, then import.
cms-export.zip
- 12 pages, 8 blocks
- 41 images, no duplicates
- revisions: off
dry-run report
On an identifier conflict you choose: skip, overwrite, or revision-only, which brings it in as a revision to publish later.
Illustrative diagrams with sample content, not product screenshots.
Everything here is built. It's in final testing now.
What comes after the first release has no dates, on purpose.
01
Moving
- Push and pull pages and blocks, one or many at once
- Images travel with the content, both ways
- Store view mapping between installations
02
Checking
- Conflict detection when the target has changed
- Code comparison and automatic visual comparison
- Preview in your real theme, on either side
03
Recovering
- A revision on every save, with its images
- Drafts, restore with backup, undo a push or pull
- Trash and restore, with full history
04
Exporting
- Export and import archives with their images
- A dry-run report before anything is imported
- Skip, overwrite or revision-only on conflicts
From the founder
[PLACEHOLDER: founder quote]
Miloš Glavinić
Founder, Foxycom · Adobe Commerce engineering
If you run Magento with more than one environment, I'd like to hear how you move content today. Write to me [PLACEHOLDER: contact address].
Straight answers.
The questions Magento teams ask us most. Anything else, ask the people who build it.
Miloš Glavinić
Founder, Foxycom
Not sure it fits your setup? Describe how you move content between environments today and ask me directly.
[PLACEHOLDER: contact address]
Can I download it now?
Not yet. Everything on this page is built and in final testing. Early Access is an interest list, not a download.
What will it cost?
We haven’t published pricing yet. Founding members get [PLACEHOLDER: founding offer, to be approved]. Joining doesn’t commit you to anything.
Which Magento versions does it support?
Magento Open Source and Adobe Commerce 2.4.6 to 2.4.9, on PHP 8.2 to 8.4.
Does it work on Adobe Commerce Cloud?
It’s built for it. Visual comparison uses hosted rendering where an installation can’t run a browser, Commerce Cloud first, and it warns you before touching Content Staging scheduled updates or Dynamic Blocks.
Does it work with Hyvä?
It moves Magento Page Builder content, whatever theme your storefront runs, Hyvä included. Hyvä CMS, Hyvä’s own page builder, isn’t supported yet. We’re exploring it.
What does it send, and where?
Content moves directly between your own installations, over an authenticated connection you set up in the admin. It doesn’t pass through a Foxycom server. [PLACEHOLDER: licence check wording, once it is final]
Can it break production?
It’s built not to. You see a comparison and any conflict before a push, every change keeps a revision, a push or pull can be undone, and images other content still uses are never deleted. Keep your regular backups anyway.
How do I remove it?
A clean uninstall removes its tables, configuration, media backups and queue messages.
Who builds it?
Foxycom, an Adobe Solution and Technology Partner based in Belgrade. We support Adobe Commerce for brands like Les Mills, and we built CMS Harmony for our own client work first.
Your next release, without the copy and paste.
Join the Early Access list to hear first when CMS Harmony is ready to install. We'll use your email only for that.
Founding members
[PLACEHOLDER: founding offer: a price or an evaluation period, to be approved]
- Priority onboarding with the engineers who built it
- A direct line into the roadmap while it’s young
- [PLACEHOLDER: number of founding places, to be approved]
Running several stores or an agency? Book a 30-minute walkthrough with the team that built it.