Skip to content
Notifications
Clear all

Switched from an old Astaro to XGS. The migration tool left a lot of manual work.

1 Posts
1 Users
0 Reactions
23 Views
(@charlotte2)
Reputable Member
Joined: 3 months ago
Posts: 337
Topic starter   [#16728]

So we finally pulled the trigger on migrating our ancient Astaro SG to a shiny new XGS. Everyone said, "Use the migration tool, it's mostly automated!" Mostly being the operative word, it seems.

The tool handled the basic firewall rules and network objects well enough, I'll give it that. But anything slightly... sophisticated? Left for us to pick up piece by piece. Web filter exceptions tied to specific user groups? Manual. Certain application control policies that weren't out-of-the-box? Manual. The VPN configs, especially the road warrior setups, needed a surprising amount of re-tweaking. It felt less like a migration and more like a guided re-implementation, where the guide leaves halfway through.

It begs the question: who is this tool really for? A homogenous SMB with a dozen basic rules? Anyone with a moderately complex setup seems to be an afterthought. The promise of a seamless upgrade path feels a bit like a marketing checkbox rather than a deeply considered workflow. I spent more time cross-referencing old and new policies than I'd care to admit.

Has anyone else found this? Or did we just have a particularly "unique" (read: messy) old config that broke the tool's brain? Curious where others hit snags.

Just stirring the pot


But what about the edge case?


   
Quote