The kind of vector work you do most should drive the choice, because logos, icon systems, signage, technical drawing, and packaging each stress an editor differently. Basic paths move easily; the hard part is keeping editability across effects, symbols, brushes, clipping masks, gradient meshes, and multi-artboard files. Inkscape is the most complete open replacement, built around SVG as its native format and running on Windows, macOS, and Linux. Graphite adds a nondestructive, node-based workflow for procedural, re-editable artwork, though it is still an alpha web editor. Akira targets UI and UX design on Linux but is early-development software, so keep it out of paid production for now.
Expect gaps around Illustrator-specific behavior. Open source editors are strong for SVG, illustration, diagrams, and many print-ready PDFs, but they may not reproduce every live effect, appearance stack, gradient mesh, or plugin-dependent step. Typography can shift too, because text engines, font substitution, and OpenType support differ between applications. Treat the change as a workflow redesign rather than a one-for-one clone of the interface.
Prepare files inside Illustrator before you leave. Keep a native archive, then export working copies as SVG or PDF depending on the target, expand appearances, embed linked images, and outline text only once editability no longer matters. After import, inspect layers, artboards, strokes, transparency, and text reflow, and budget cleanup on complex artwork. If clients contractually require native Illustrator files, confirm that in scope before switching, because an open tool may satisfy the design but not the deliverable.