Map it. Validate it. Understand it.
Separate transformations from validation, make every conversion explainable, and design useful errors around an explicit destination contract.
Read the guideImport Notes · Category
Data engineering
Start at the destination contract. These guides connect record identity, schema mapping, validation, and job outcomes so you can explain what an import will change before writing anything. Read the introduction first, then work through field mapping with a small dataset that includes both accepted and rejected records.
What is an import API?
Turn external records into clear, validated application data. A practical introduction to contracts, transformations, errors, and job lifecycles.
Read the guideMake the reading practical
Choose one representative source from your own workflow, remove sensitive information, and compare its requirements with the examples in these guides. Write down the expected destination values before deciding which transformations to automate.
Use the local mapping example for a small first exercise. The reading paths connect these topics to broader implementation questions.