Cura to PrusaSlicer

Convert first. A Cura file holds one plate; the converted one re-anchors it on a PrusaSlicer bed and welds Cura's loose triangles into a solid mesh.

Do I need to convert first?

Yes. Converting translates Cura's settings into PrusaSlicer keys and maps each extruder train to a tool. Then read the Notes table for anything left out.

What carries over from Cura to PrusaSlicer?

• Plate: one, re-anchored between Cura's bed origin and PrusaSlicer's.
• Filaments: one extruder per tool. Cura's 0-based extruder numbers are read as slots. If the printer has fewer tools, extra filaments merge onto kept ones of the same material, then the nearest colour. Pick the same filament twice to share a slot.
• Geometry: Cura writes one vertex per triangle corner, which PrusaSlicer reads as an open surface. The download welds it into an indexed mesh.
• Object settings: translated key by key from Cura's per-model section. A key with no match in PrusaSlicer stays out.

What does PrusaSlicer lose?

Cura declares no modifier volumes and writes no layer-range file, so neither has anything to carry. Cura paints with a texture, not per triangle, and preslice does not convert it to PrusaSlicer paint.

Which PrusaSlicer settings stay at default?

Any key Cura cannot express, for example support_material_interface_layers at 3 (PrintConfig.cpp). A tool cap also adds N tool changes dropped and Purge volumes / recalculated rows.

What are the shared losses?

See what a conversion cannot carry. To go the other way, read PrusaSlicer to Cura.