Bring your history into RENMA
Keep the originals. Convert supported contents. Review before applying.
1. Save a backup first
Keep the source export unchanged. If you already use RENMA, save a RENMA backup before an import. An old RENMA backup should be handled as a Restore file, not silently converted into an additive import.
2. Use the guide from your app version
Open RENMA’s Data / AI Bridge area and use its conversion guide or export pack. It describes the format accepted by that app version. You may give that guide and the records you choose to an external AI. RENMA does not upload them for you.
3. Ask for faithful conversion
Keep dates, units, left/right differences, machine identities and custom values where supported. Missing values must remain missing or be clarified with you. Ask the AI to identify anything it cannot represent. An AI response alone is not proof that a file is valid.
4. Check the Preview
Select the resulting file in RENMA. Check the date range, workout and set counts, exercises, units and any setup changes. Correct or cancel if they differ from your source. Validation and Preview do not apply changes.
5. Approve, then check the history
Apply only after you have checked the whole batch. Compare the imported records with the source. Undo is available only when RENMA can safely reverse that import; later edits or a Restore can prevent it. A backup remains your recovery path.
Formats and plan limits
Bridge receives files that follow the supported RENMA contract, not every arbitrary CSV or JSON. Free imports have an allowance; Pro / Lifetime imports are unlimited. Validation, Preview, cancellation and failed imports do not consume an import allowance. Files containing custom fields or machines require Pro / Lifetime. Check the app for your current allowance and trial state.