These pages describe how to import data to SecuTix 360.

• Data can come from many data sources (Excel files, your previous ticketing system, other database, ...).
• You can import contacts or sales information (sales, memberships, season tickets, etc.)
• Detailed information about file formats is provided in these pages.
• Depending on the data you import, there will be some configuration to do in SecuTix 360
• It is important that the data to be imported are cleaned before import to assure high quality so that it can be used efficiently by the marketing tools.
• It is important that the data to be imported comes with reports allowing for validation of the imported data, otherwise we can't guarantee that the import is exhaustive.
• These reports, which must be representative of the data to import, must be generated at the time the data are extracted, so the comparison between reports and imported data is effective.
• These reports will also be used during your acceptance phase in a preproduction environment so you can validate the completeness of the imports.

We import the following item:

• Contacts
• Sales as a criterion
• Sales as single entries and performances
• Sales - Vouchers
• Sales - Pass Visit
• Sales - Season tickets
• Sales - Memberships
• Sales - Non dated pass
• Sales - Services
• Sales - Open products
• Barcodes imported in Access control system

During the onboarding phase, we import the data first on preproduction so that you can review it during an acceptance phase.

If you're OK with it and eventually after some corrections, we'll import data on production just before the go-live.

Two (2) imports are included in the service: 1 import in preproduction (rehearsal) and one import in production (go live).

As opposed to Standard import services, the provided data needs to be mapped, extracted, grouped and filtered correctly to fit SecuTix Standard import files.

Special sercices need a preliminary analysis to propose an action plan and a commercial proposal, based on the complexity of the provided data.

More than one rehearsal and validation pahse may be required, providing the adequate reports for validatioan and your involvement in the acceptance phase are of a key importance.

We accept the following data formats to be imported.

• CSV not SecuTix formatted
• Excel
• Rodrigue database dump
• SecuTix 1
• Any Oracle, SQL Server, MySql, Postgresql, Filemaker, Access database

During the onboading phase the contacts from your old system are imported in SecuTix 360. In addition to the contacts, some sales data can be imported in certain cases.

After the onboarding phase, contacts can be updated or new contacts can be imported

Image RemovedData import process and planning

1. At the internal project kick-off, the project leader announces which data will be migrate (Individuals contact, structures, selling history as indicators)
2. The team leader inform the customer and give the links to the documentation in Concluence to the customer
3. The customer fills the files and gives the data in the SecuTix format to the project leader 
4. No later than two weeks before milestone J, the project leader creates a kayako data import with the data
5. If the customer is not able to give the data in the SecuTix format, The customer delivers his format and a special price is communicated to the customer (Ask FLO)
6. CSVN verifies the data and transforms the data by scripts or excel formulas. There is no individual modification. Every modification is reproducible with the scripts or excel formulas. Only entire columns are modify. No individual modification is done on a line
7. CSVN imports the data in a development environment to validate the import process. VN correct the scripts and formulas to solve the imports problems.
8. The quality gate in CSVN verify the log file and the protocol used (scripts and excel formulas applied to transform the data) Actions are taken in CSVN if corrections are necessary
9. No later than one week before milestone J, CSVN import the data into the pre production environment (pre condition: The copy of data Institution and basic configuration) from prod – to preprod is done before.
10. CSVN update the kayako with the list of non-imported data (Log file), set the kayako to “final validation” and set the owner to the project leader
11. J-2: The customer validate the data import in pre-production
12. Optionally, to import recent data, the customer has the possibility to give a second full data extraction at J-1 in the same format than the first data extraction. VN execute the same scripts on the data.
13. J : CSVN imports the data in production
14. CSVN update the kayako with the list of non-imported data (Log file), set the kayako to “final validation” and set the owner to the project leader
15. The project leader validates the import, transmits to the customer and set the kayako to “solved”. 

Data planning

J-14: The customer deliver the cleaned data in SecuTix format

J-7  : CSVN imports the data in the pre production environment

J-2  : The customer validate the data import in production n

...