<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1098210340196579&amp;ev=PageView&amp;noscript=1" Lead Track when a user expresses interest in your offering (ex. form submission, sign up for trial, landing on pricing page) fbq('track', 'Lead');>
  • Data that does not map to existing Apto fields will be migrated to a rich-text field for reference. No additional custom fields will be created.
  • Data review call with Data Analyst to walk through the data that was imported
  • Data must be delivered in one of the following file formats:
    • One Spreadsheet (.xlsx file) with one worksheet of data. Client is responsible for consolidating data into one worksheet.
    • One database backup (.bak, or .accdb file).
    • One flat file (.csv, or .txt file). Multiple flat files will be accepted as one data source if it meets both criteria below:
      • All files were exported from the same platform.
      • All files are related by a system of unique database IDs/keys. Business logic, such as relating by name, address, or combinations of fields does not qualify as a unique ID.
  • Data must be in row and column format. Crosstab or aggregate data cannot be imported. Data must not contain the following: subheadings, summary or total rows, color-coding, etc… as these cannot be translated in migration.
  • If the data format or integrity prevents it from being imported, the client may need to clean or consolidate the data prior to migration. Apto will communicate this at the time of migration.