Complete Import and export requirements | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/client-discovery-project-briefing-custom-software-brief-software-import-export Publisher: Pixie Technologies LLC Custom software development brief Complete Import and export requirements Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Describe source files, mapping, CSV/PDF/Excel outputs and migration needs. Audience: CRM administrators, project teams, developers, authorised client contacts and public prospects; Permission: Secure-link recipient; Module v1.1.1; Where to goSecure recipient link → Custom Software Development Brief Before you start - Verify 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 helps you do 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. Follow these steps - Go to Secure recipient link → Custom Software Development Brief. - Go to the relevant custom-software section section containing Import and export requirements. - Enter or select Import and export requirements using the supported value described below. - Continue to the next step or save the current brief so autosave records the value. - Reopen the brief or review page and confirm the value is shown correctly. Fields and options Import and export requirementsDescribe source files, mapping, CSV/PDF/Excel outputs and migration needs. Rules and limits - 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. Check it worked - 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. Related guides Complete Data entities (https://pixiecrm.com/help-centre/client-discovery-project-briefing-custom-software-brief-software-data-entities)Complete Existing systems (https://pixiecrm.com/help-centre/client-discovery-project-briefing-custom-software-brief-software-existing-systems)Custom software development brief (https://pixiecrm.com/help-centre/topic/client-discovery-project-briefing-custom-software-brief)Browse all Client Discovery & Project Briefing Portal guides (https://pixiecrm.com/help-centre/category/client-discovery-project-briefing)Client portal overview (https://pixiecrm.com/help-centre/client-portal-overview)Add and manage customer contacts (https://pixiecrm.com/help-centre/add-and-manage-customer-contacts)Configure customer contact permissions (https://pixiecrm.com/help-centre/configure-customer-contact-permissions)Upload and share customer files (https://pixiecrm.com/help-centre/upload-and-share-customer-files)Configure SMTP email delivery (https://pixiecrm.com/help-centre/configure-smtp-email-delivery)Review email delivery issues (https://pixiecrm.com/help-centre/review-queued-email-and-delivery-issues)