01
Databases
A model drawn from how you operate: linked tables, one key per record, a date on anything that changes.
Duplicate customers, files re-entered every week, years of history locked in old software. Witify and Kashika Studio, its data division, build the databases and data flows that put your data in order and keep it right.
Over 1.9billion
dated measurements in HEC Montréal’s MID database Every row keeps the date of the delivery that brought it.
170
weekly deliveries recorded since August 2023 21 files per delivery, loaded into the database in the same order every week.
97
data sources imported for the Observatoire des tout-petits Ten providers, over 80% of sources in Excel, each with its own layout.
Over 560
published versions kept At the Observatoire, every release of an indicator stays on record.
One record in the accounting software, another in the sales spreadsheet, a third on the website. Each has its own address. Nobody knows which one is current.
A supplier sends its prices in Excel, a partner its sales in CSV. Someone copies them over line by line, with the mistakes that come with it.
Access, FileMaker or an in-house tool: years of data sit there, organized in a way nobody really remembers. Our article on the risks of Access in 2026 covers the options.
Management and accounting arrive at two different totals for the same month. The meeting goes into finding the right one, and the decision waits.
The new software waits because nobody can promise the history will follow. The old system stays, for lack of a better plan.
If a well-kept spreadsheet is enough, we will tell you. A database earns its place when several people, several tools or several years have to rely on the same numbers.
The move is decided on those criteria, not on the size of the company.
01
A model drawn from how you operate: linked tables, one key per record, a date on anything that changes.
02
Excel, CSV or partner exports: every row is read and checked. Differences are shown before anything is written.
03
Accounting software, online store, CRM: data moves between tools through APIs, with a log of every send.
04
Rules flag duplicates, empty fields and inconsistencies. A person confirms every correction.
05
Data from the old system moves to the new one, history included. Totals are compared with the source before the switch.
06
A backup every day, access by role, sensitive data encrypted.
Once in order, your data can answer other questions. Each use has its own service, with the same team.
A written plan: what your data lets you decide and which projects come first.
A precise question, then a written answer, backed by evidence and a stated degree of certainty.
Dashboards and charts your teams open on their own.
When the volumes outgrow what a single database can carry.
Imports
The log keeps each delivery with its start time, duration and steps. An incomplete delivery is never half loaded: it is marked skipped, with its reason, and the next one goes through.
Duplicates
The system spots records that look alike. A person picks the right values. The orders follow the record that is kept.
Integrations
When the accounting software rejects a record, it is counted and listed with the reason. Nothing disappears quietly.
Distribution MA: eight kinds of documents sent to QuickBooks
Quality
Malformed emails, orders without a customer, likely duplicates: every night, the rules reread the database. Gaps are put forward for correction, never fixed behind your back.
01 Discovery
One file per customer, in every tool
EssentialSee the history of prices granted
EssentialFind an order from five years ago
LaterStop retyping the online store’s sales
EssentialThe same totals as management
EssentialKnow when a send fails
ImportantA monthly report nobody argues about
EssentialKeep the old software’s full history
ImportantAdd a new partner’s file
Later02 Analysis
03 Data model
04 Mockups
05 Specification
As a buyer, I want to import the supplier price list and see the changes before they apply, so that no price changes without my knowing.
06 Development
Nightly quality report
Quality NKArchive inactive records
Customers SRCompare the price list before import
Imports ABSuggest likely duplicates
Quality ODSend customers to the accounting software
Integrations SRCustomer takeover from the old software
Migration ODChange history of a record
Customers NKStop at the invalid row
Imports AB07 Quality
Widely used technologies, chosen for the project and for what is already in place. See our technologies
Document reading, assistants, automatic classification: our AI integration service first puts a figure on the time saved, then builds what justifies it.
01
We review with you where data is still copied, reconciled or corrected by hand. Then we suggest what to connect next, starting with what costs the most hours.
02
Fewer duplicates, imports with no rework, reports ready sooner: we track what each change delivered, against your own indicators.
03
New connectors, AI models that can read your files, analysis tools: we sort through them and bring you only what suits your data.
04
A new source, a new indicator, an acquisition: the database grows without losing its history.
At HEC Montréal, a research database takes in measurements for thousands of artists every week. At the Observatoire des tout-petits, every file received is compared with the database before import. At Original Garage Motosport, each part is counted in one place, which tells Shopify what can really be sold. Each case study shows the screens and choices that keep this data sound.
Very satisfied with the service offered by Witify. We developed an inventory management system that has truly transformed my company’s data. Exceptional and fully satisfying service!
The questions that often come before a first import or a migration.
Another question? Write to us at info@witify.io or call 1 800 334 9031.
We start with an inventory: what the old system holds, what must follow and what can stay archived. Each field is then mapped to its place in the new database, dates and versions included.
The data runs through a copy of the new database several times. Each trial is counted and compared with the source. Every gap is explained, then fixed. The old system stays in place until your team approves the switch-over.
If your data lives in Access, our article on the risks of Access helps you gauge the urgency. For a full application, see our application modernization service.
First, each kind of data gets a single source: customers in one tool, prices in another. The other software receives a copy, kept current through an integration.
Then, matching rules suggest records that look alike. A person confirms each merge. Imports are checked on entry, then a quality report flags what still needs fixing.
The real starting point is often elsewhere: agreeing with your teams on what an active customer or a discontinued product means.
The systems we host generally run on servers in Canada, with DigitalOcean or AWS, whose hosting is certified ISO 27001 and SOC 2. An automatic backup runs every day. Sensitive data is encrypted.
Each person opens only the screens of their role. Every change is written to the audit log, with its date and author. If needed, we sign a confidentiality agreement before seeing your data.
For compliance questions, such as protecting personal information, see our data strategy service.
Both have their place. Excel remains the right tool for analysis, what-if scenarios and quick fixes. A database becomes useful when several people edit the same records, when history matters or when every file received has to be checked.
Keeping Excel at the entry point is common: the Observatoire des tout-petits’ platform receives mostly Excel workbooks, which it reads and checks before loading them into the database. Our article on the limits of Excel helps sort things out.
First, clear objectives: what you want to discover or solve with this data. Next, the types of data that answer them: demographic, behavioural, transactional and so on.
You also need a place to collect and keep it. Depending on the volume and the number of users, that ranges from an Excel sheet to a database, or even an analytics platform.
Collection must respect the privacy rules of your region: consent obtained, personal data protected.
Finally, you need expertise to interpret and use the data collected: an analyst, a data scientist or a team like ours.
Yes. We connect to your warehouse to extract, transform and load the data your analysis and visualization tools need. Whether it runs on your premises or in the cloud, we work with the infrastructure in place.
If needed, we also help you manage it better: better structured tables, quality checks, access by role.
Yes. A visualization can update as the data arrives, to track performance, monitor an activity or detect an event.
It takes a configuration specific to each source and close coordination with your teams, so the connection stays stable and secure. Our data visualization service covers this side in detail.
Five factors weigh the most.
Our business and technical analysis sizes these factors for your project before it is priced.
For simple to moderate needs, yes. Power BI and Looker Studio (formerly Data Studio) are user-friendly, require no programming and produce good dashboards.
For deeper analysis, such as machine learning, forecasting or very large volumes, you may need tools like Python, R or d3.js. Either way, an analysis is only as good as the questions asked and the data at the source. See our data analysis service.
Show us the file re-entered every week, the old system that holds the history or the two reports that contradict each other. An expert looks at them with you and suggests a first step. If needed, we sign a confidentiality agreement before seeing anything.
Free. No commitment. Reply within 24 hours.
Names and figures shown in the interfaces are examples.