- Home
- Switching to calServer: take over your data instead of retyping it
Data migration
Switching is the trickiest part.
That is why it is guided and runs in steps you can check: connect the source, look at the data first, take it over module by module, test run before going live.
- Connect MET/TEAM, upload MET/BASE as a file
- Excel with column mapping instead of a fixed format
- Migration from the older calServer generation
- A test run before you go live

How a data migration works
No switch on a single cut-off day. Each step can be checked on its own, and you can stop at any time.
- 1
Connect the source
Step 1
We set up access to the current system: MET/TEAM, MET/BASE, an existing calServer installation or a set of Excel files.
- 2
Look before anything happens
Step 2
You can view the source tables in advance. You see what is in them before anything is taken over.
- 3
Map the fields
Step 3
Your columns are mapped to calServer fields. Whatever does not fit is created as an extra field instead of being thrown away.
- 4
Take over module by module
Step 4
First master data, then instruments, then history. Each module separately, with a log and an error list.
- 5
Test run and comparison
Step 5
You check samples against the current system. Only when they match do you switch over.