InnerWeb
Skip to main content

Card migration stages: implementation notes for the IT project manager

An IT project manager running a card migration needs the order of stages, the conditions for moving on and the split of roles. Below are implementation notes for the five stages: inventory, a pilot on one gate, the employee wave, external contractors and retiring the old format.

5
migration stages
Source: sample plan
2-10 wks
software installation time from the order
Source: offer sheet

Plan assumptions

The sample plan has five stages. The plant in the calculation has 1,000 employee cards, 300 external contractor cards and 20 readers. The plan is a template to adapt, not a description of a completed project.

InnerWeb is a software producer and does not manufacture or replace access control readers. In this project it provides the intake of punches from the access control system, their linking into working days, schedules, exceptions and reports.

Stage 1: inventory

Goal: a complete set of data on cards, readers and people. Condition for moving on: an inventory of cards with object code and number, and a personnel number for every active card. On the access control vendor's side: the card export. On the InnerWeb side: the CSV import format and the reader dictionary.

Pitfall: cards without an owner and people with two cards. Resolve them before the pilot, not during it.

Cards covered by each stage of the sample plan

Cards covered by each stage of the sample planHorizontal bar chart: 100 cards in the pilot, 900 in the employee wave, 300 in the external contractor stage02004006008001000cardsPilotPilot: 100 cards100Employee waveEmployee wave: 900 cards900External contractorsExternal contractors: 300 cards300
Source: Sample calculation: split of 1,300 cards as a planning assumption

Stage 2: pilot on one gate

Goal: check the new card, the reader and the flow of punches on one gate with low traffic. Condition for moving on: punches from the new gate are visible in time recording, the direction is recognised correctly, and there are no unknown cards in the queue. On the access control vendor's side: the reader and its configuration. On the InnerWeb side: receiving HTTPS POST messages and checking working days.

Pitfall: a pilot without an acceptance criterion. Write down a threshold, for example zero unexplained punches for one week, before starting the wave.

Stage 3: employee wave

Goal: replacement of the workforce's cards shift by shift or department by department. Condition: dates agreed with HR, an issue point and duty. On the access control vendor's side: personalisation and issue of cards. On the InnerWeb side: assigning numbers through a CSV import and monitoring the "card to be assigned" queue.

Pitfall: replacing readers at the next gates before cards have been handed out. Cards first, then gates.

Stage 4: external contractors

Goal: replacement of external contractors' cards on a separate date, with contract supervisors. Condition: a list of contractors and their employees with numbers. On the access control vendor's side: issue of cards. On the InnerWeb side: attendance reports for external contractors and, if the plant chooses, guest registration with QR codes instead of physical cards.

Pitfall: assuming that external contractors will replace cards as quickly as the workforce. They usually need a longer window.

Stage 5: retiring the old format

Goal: switch off reading of the old technology (125 kHz) on the readers. Condition: zero punches from old cards over an agreed period. Only this stage improves security, because 125 kHz cards transmit a fixed number without authentication, while MIFARE DESFire EV2 and EV3 cards use AES encryption and mutual authentication.

Pitfall: switching off without checking the punches. A summary of punches from old cards over the last few weeks is a precondition of the decision.

Contract and installation time on the software side

For schedule planning it is worth knowing the parameters on the InnerWeb side: an open-ended contract with monthly notice, licences counted by active users, installation within 2-10 weeks from the order. BLE-active cards, if the plant decides on location tracking, are separate devices from the access control cards: 220 PLN net one-off, housing 40 PLN net (indicative ranges from 2025-2026 deployments; individual quotation). The card printer is provided by a proven supplier or by the client's own devices, if they meet the requirements.

Video

Frequently asked questions

Can the pilot be skipped?

It can, but the risk grows. A pilot on one gate detects problems with the number format, direction and card assignment before they reach the whole workforce.

Who is responsible for replacing readers?

The access control vendor. InnerWeb integrates with the access control system and does not replace readers.

When should the old format be retired?

When the old cards have produced no punches for an agreed period and the queue of unknown cards is empty or explained.

Sources

Write out the migration stages with us

We will prepare the split of roles and the punch specification for the access control vendor. Book a conversation with the InnerWeb team.

Let's talk