Britixo CRMBritixo CRM Enterprise Help Centre
Help centreClient Discovery & Project Briefing PortalComplete Import and export requirements
Custom software development brief

Complete Import and export requirements

Describe source files, mapping, CSV/PDF/Excel outputs and migration needs.

Audience: CRM administrators, project teams, developers, authorised client contacts and public prospectsPermission: Secure-link recipientModule v1.1.1
Exact navigationSecure recipient link → Custom Software Development Brief
Before you begin
  • Confirm the module is active and use the exact navigation shown above.
  • Use an account with the stated module and core CRM permissions.
  • Use known test records when changing statuses, visibility, saved filters or global navigation.

What this guide covers

Describe source files, mapping, CSV/PDF/Excel outputs and migration needs. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Secure recipient link → Custom Software Development Brief.
  2. Go to the relevant custom-software section section containing Import and export requirements.
  3. Enter or select Import and export requirements using the supported value described below.
  4. Continue to the next step or save the current brief so autosave records the value.
  5. Reopen the brief or review page and confirm the value is shown correctly.

Fields, choices and supported possibilities

Import and export requirementsDescribe source files, mapping, CSV/PDF/Excel outputs and migration needs.

Code-backed validations and workflow rules

  • The field is stored as part of the current request or intake answer set.
  • Leave an optional field blank only when the form permits it; required fields must pass server-side validation.

Expected result and verification

  • The complete import and export requirements workflow completes without a validation, permission, ownership or availability error.
  • The related record, portal view, activity entry, notification log or API response shows the expected state.
  • Client-visible, public and API data remains limited to the code-backed ownership and visibility rules.

Security, privacy and operational checks

  • Use controlled test records and non-production credentials before wider rollout.
  • Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs.
Complete Data entitiesComplete Existing systemsCustom software development briefBrowse all Client Discovery & Project Briefing Portal guidesClient portal overviewAdd and manage customer contactsConfigure customer contact permissionsUpload and share customer filesConfigure SMTP email deliveryReview email delivery issues