Software development.
Custom applications, integrations and data systems. Repairs and maintenance for existing business software.
Build a project briefAn integration field map.
A field map records what a connector transfers and how each value is converted. Use it to agree which system owns each field before development starts.
This original sample can be downloaded and adapted to your applications. It contains field definitions, not customer records.
Download the sample CSVExample document. Source and destination names are illustrative.
| Source field | Destination | Conversion rule |
|---|---|---|
customer_id | external_ref | Preserve the source identifier |
email | email | Trim spaces; validate format |
company_name | display_name | Trim surrounding spaces |
status | is_active | Map active and inactive values |
updated_at | source_updated_at | Convert to UTC timestamp |
Scroll the table horizontally to view all fields.
Calculate API request batches
This counts batches of records. Check the API’s batch limit; authentication, lookups and retries can add requests.
Your settings stay on this page.
6 requests with 200 records each, and 1 request with 50 records.
- Request 1200 records
- Request 2200 records
- Request 3200 records
- Request 4200 records
- Request 5200 records
- Request 6200 records
- Request 750 records
Full bar: 200 records.
Project delivery
The scope lists the software to be supplied and the checks used to accept it. Delivery also includes the material needed to run and maintain the code:
Project scope and deliverables- Source
- Application, connector or script code in the agreed repository.
- Configuration
- Runtime requirements, environment variable names and deployment steps.
- Verification
- Behavior checks, representative inputs and migration reconciliation.
- Operation
- Data mappings, logs, recovery procedures and maintenance notes.