Transfer from other software

Move your existing operation into Repulion.

Most transfers start with the data you already have. Export existing data, map the fields and import the records into Repulion through a controlled migration process.

A practical migration

CSV is usually the fastest route.

Aircraft, people, memberships, training records and other structured data can be prepared from exports you already use. We map the fields before anything is imported, check the result and only then move the records into the live organisation.

Where a system can provide another structured export or an API, that can be used as well. The aim is simple: keep the history that matters and avoid unnecessary manual entry.

members.csvField mapping
Current fileRepulionStatus
member_namePerson nameMapped
emailEmail addressMapped
licence_expiryDocument expiryMapped
member_typeOrganisation roleReview

A controlled transfer, not a blind import.

The data is checked before it becomes part of the operational record.

01

Export

Take a CSV or another structured export from the system you use today.

02

Map

Match columns and record types to the corresponding fields in Repulion.

03

Validate

Check missing values, duplicate records, date formats and data that needs a decision.

04

Import

Load the approved data into the organisation and verify the result before normal use.

Bring across the records that matter.

The exact transfer depends on the system you are leaving and the quality of the export it provides.

Aircraft & fleetRegistration, aircraft details and relevant operational starting data.
People & rolesMembers, students, instructors, administrators and organisation roles.
Training recordsStructured student and programme records where suitable source data is available.
DocumentsDocument metadata, expiry dates and verification information.
Finance dataRelevant balances, billing references or structured invoice data where required.
Other structured recordsAdditional data can be mapped when the source system provides a usable export.

Before go-live

You should know what moved, what did not, and why.

Mapping reviewSource fields are agreed before import.
ValidationProblem rows can be corrected before the live transfer.
Clear cut-overAgree when the old system stops being the operational source.
Export retainedKeep the original source export as a migration reference.

Planning a switch?

Send us a sample export and tell us which system you use today.

Talk about a transfer