Importing Lifecycle records
Use this to import an employee's history, such as past promotions, transfers and salary changes, onto their Lifecycle tab. Lifecycle used to be called Career Progression. Importing is how you bring that history across when you move to KAMI, or add many past records at once, so a record starts with someone's career and not with the day you switched systems.
Where:
- From any employee: their profile › Lifecycle › Import history
- With other bulk data: My Team › Settings, under Bulk tools › Profile Import/Export › Lifecycle
You need:
- Edit access to the Employment right
- To use Profile Import/Export, also the Bulk Profile Data right and Edit access to the Personal right
Which one, when
| You want to | Use |
|---|---|
| Load many past changes from a file | Lifecycle import |
| Add or correct one record | Add a record, or the pencil on the row, on the employee's Lifecycle tab |
| Record a change happening now | The employee's profile, or Profile Manager |
| Load current details, not history | The main bulk data import |
⚠️ A Lifecycle record is history. It does not change the employee's current role, pay or placement. Payroll does read Wage records when it splits a salary change in the middle of a cut-off, so check those dates with care.
How to import Lifecycle records
- Open any employee's profile and go to the Lifecycle tab.
- Select Import history.
- Select Download Template.
- Add one row per record, using the columns below. One file can cover many employees.
- Select Browse file and choose your file.
- Select Import.
- Wait for the Data Import email, and read it. Then refresh the Lifecycle tab.

What goes in the worksheet
| Column | Required | What to enter |
|---|---|---|
| EmployeeID | Yes | The employee's ID in KAMI |
| Effective Date | Yes | When the change took effect |
| Description | Yes | What happened, for example "Merit increase" |
| Field | Yes | What changed: see below |
| Old Value | No | Leave blank if there wasn't one |
| New Value | Yes | The value from that date on |
| Remarks | No | Anything else worth keeping |
Field can be any of three things:
- A standard field: Position, Department, Branch, Subsidiary, Cost Centre, Wage, Employment Type, Probation Period, Hire Date, Termination Date or Contract Expiry Date.
- One of your company's custom job fields, if it is set to Record in Lifecycle.
- Any name you choose, when the change doesn't belong to a field, such as "Dean's Award".
Hire Date, Termination Date and Contract Expiry Date take dates as YYYY-MM-DD. So does a date custom field. Wage and Probation Period take a number that isn't negative. A custom field's value must suit its type.
How to add past probation dates
KAMI saves a Probation ended record by itself on the day someone passes probation. It does not create one for anyone who passed earlier, because hire date plus probation period would only be a guess: people are regularised early, late, or hired as regular.
- Add a row with Probation ended as the Field.
- Enter the date as both the Effective Date and the New Value.
- Add a Description, then import as above.
Before You Start
Decide how far back to go. Full history is ideal and rarely available. The practical answer is usually the current role plus the last few changes.
Have the dates right. Lifecycle is a dated series. Wrong dates produce a history that reads plausibly and is wrong, which is worse than no history at all.
What Happens Next
- If any row has an error, nothing is saved. A wrong EmployeeID or a value that doesn't suit its field rejects the whole file. The Data Import email lists the errors, so fix them and import again.
- Records appear on each employee's Lifecycle tab, oldest first.
- Importing the same employee, Field and Effective Date again updates that record instead of adding a second one.
- Importing from this window always uses Append. It never deletes what is already there.
Tips
- Import ten people first and read their records. A date or column mismatch shows up on ten and hides on four hundred.
- Check your Field spelling. Any name is accepted, so "Wages" becomes a record called Wages and not a Wage record.
- Use one name for one thing. "PAN Transaction" and "PAN Trans" are separate records and sort apart.
- Keep the source file. It shows where the history came from if someone queries it later.
- Do not import history you cannot vouch for. People rely on this record for promotion and pay decisions.
Troubleshooting / FAQ
Q: How do I add career history or past promotions? Follow the import steps above. For a single record, use Add a record on the Lifecycle tab.
Q: I imported the file and no records appeared. Read the Data Import email. If one row was wrong, nothing was saved. Otherwise, refresh the tab, because rows appear once the file has been processed.
Q: Records imported but the employee's current role is unchanged. Expected. Update current values on the profile or in Profile Manager.
Q: I can't see some Wage records. Wage changes are hidden from anyone without access to pay. The tab tells you how many are hidden.
Q: Why has Probation ended gone from some employees? It used to be worked out from the hire date and probation period. It now shows only when a record exists, so add or import the dates you want on record.
Q: Can I link a letter to a record? Yes, one at a time: use Add a record or the pencil on the row, and choose one of that employee's documents.