DESCRIPTION OF SERVICES 1. Introduction The Agency has an on-premise installation of Claris FileMaker Server v13 software. The Agency needs to recover administrative-level user access to this ...
DESCRIPTION OF SERVICES 1. Introduction The Agency has an on-premise installation of Claris FileMaker Server v13 software. The Agency needs to recover administrative-level user access to this ...
Filemaker Claris information
What are typical collaboration dynamics for a FileMaker Claris developer within an organization?
FileMaker Claris developers often work closely with stakeholders such as project managers, end-users, and other IT professionals to gather requirements and implement custom database solutions. Collaboration commonly involves regular meetings to review project progress, discuss technical challenges, and refine user workflows. Developers may also provide training or ongoing support to users, ensuring that solutions align with business needs. Team structures can range from small IT departments to larger cross-functional groups, offering opportunities to contribute to various phases of the software development lifecycle.
What is the difference between Filemaker Claris vs Database Developer?
| Aspect | Filemaker Claris | Database Developer |
|---|---|---|
| Credentials | Certifications in Filemaker/Claris | Database design and development certifications (e.g., Microsoft, Oracle) |
| Work Environment | Small to medium business, custom app development | Various industries, enterprise or custom database solutions |
| Industry Usage | Used for creating custom database apps within organizations | Designs, develops, and maintains databases across industries |
| Search Intent | Filemaker Claris vs Database Developer |
Filemaker Claris professionals focus on creating custom database solutions using Claris Filemaker, often for small to medium businesses. Database Developers have broader skills in designing and maintaining various database systems across industries. While both roles involve database work, Filemaker Claris specialists typically work within the Claris ecosystem, whereas Database Developers may work with multiple database platforms.
What are Filemaker Claris developers?
Filemaker Claris developers are professionals who specialize in designing, building, and maintaining custom database solutions using the Claris FileMaker platform. They help organizations streamline workflows, automate processes, and manage data efficiently by creating tailored applications. These developers often work closely with clients to understand their business needs and translate them into functional, user-friendly FileMaker solutions. Their expertise can include scripting, integration with other systems, and deploying solutions on desktop, web, and mobile devices.
What kind of jobs in media bring in $150,000 a year?
In media, high-paying roles such as senior media executives, creative directors, or specialized technical roles like media software developers can earn $150,000 or more annually. These positions often require extensive experience, advanced skills, and sometimes certifications, with salaries influenced by the size of the organization and geographic location.
What are the key skills and qualifications needed to thrive as a FileMaker Claris Developer, and why are they important?
To thrive as a FileMaker Claris Developer, you need expertise in database design, scripting, and application development, typically backed by experience with the FileMaker platform and relevant certifications. Familiarity with FileMaker Pro, FileMaker Server, Claris Connect, and integration with APIs or external SQL sources is essential. Strong problem-solving skills, effective communication, and attention to detail set standout developers apart in this role. These skills ensure robust, efficient, and user-friendly custom solutions that meet diverse business needs.
Does Claris own FileMaker?
Claris International Inc. owns FileMaker, which is a database software platform. Claris was formerly a subsidiary of Apple Inc. and now operates as an independent company focused on developing and supporting FileMaker solutions for users and developers.
How much does a FileMaker developer make?
A FileMaker developer's salary typically ranges from $60,000 to $100,000 annually, depending on experience, location, and certifications. Skilled developers with advanced knowledge of FileMaker Pro and related tools may earn higher salaries, especially in enterprise environments or with specialized skills.
Does Apple still own Claris?
Claris was a software subsidiary of Apple Inc. that was rebranded as FileMaker in 1998. Apple no longer owns Claris; it sold the company in 1998, and Claris/FileMaker operates independently today, focusing on database software and solutions. As a Filemaker developer or administrator, understanding its history can be helpful, but the company is now separate from Apple.
What are popular job titles related to Filemaker Claris jobs in Texas? For Filemaker Claris jobs in Texas, the most frequently searched job titles are:
What job categories do people searching Filemaker Claris jobs in Texas look for? The top searched job categories for Filemaker Claris jobs in Texas are:
Part-time
Posted 14 days ago
Job description
Working Title: Database Administrator 1 - Part Time
Location will be at - 1601 Congress Ave., Suite 3.500 Austin, Texas 78701 - Telework
Duration : Services are expected to start 10/20/2025 and are expected to complete by 12/15/2025. Total estimated hours per Candidate shall not exceed 120 hours. This service may be amended, renewed, and/or extended
I. DESCRIPTION OF SERVICES
1. Introduction
The Agency has an on-premise installation of Claris FileMaker Server v13 software. The Agency needs to recover administrative-level user access to this software and then port the database running on it to FileMaker Cloud. This project would occur in three successive phases.
In Phase 1 of the project, project staff will recover administrative-level user access to FileMaker Server v13. Project staff will then create new administrative-level user access credentials for the Agency. Finally, project staff will create two (2) backups of the database running on the FileMaker Server software.
In Phase 2 of the project, project staff will create a new database for the Agency on the FileMaker Cloud platform. This database will be identical to the structure (schema) of the Agency's existing on-premise FileMaker database.
In Phase 3 of the project, project staff will upload a copy of the Agency's on-premise FileMaker database to the new FileMaker Cloud database created in Phase 2. Project staff will then verify the success of the database transfer to the cloud via a series of verification checks.
2. Background
The Agency desires to modernize its database infrastructure by moving to FileMaker Cloud. To do this, the Agency needs project staff to access its instance of FileMaker Server v13 and backup the database running on it, create a new instance of its database on the FileMaker Cloud platform, and then transfer a copy of its existing on-premise FileMaker database to FileMaker Cloud.
The Agency's existing on-premise database has approximately 7,300 records. Each record has the same forty-five (45) fields:
The database does not appear to have any container fields. The Agency already has a subscription to FileMaker Cloud.
3. Scope of Work
3.1. Phase 1: Recover Admin-Level Access to FileMaker Server
Project staff will gain administrative-level user access to the Agency's on-premise instance FileMaker Server v13 and create a new set of administrative-level access credentials for the Agency. Project staff will then create two local backups of the Agency's FileMaker database.
3.1.1.Recover administrative-level user access to FileMaker Server v13.
3.1.2.Create one (1) set of administrative-level user access credentials to FileMaker Server.
3.1.3.Create two (2) backups of the database running on FileMaker Server.
3.2. Phase 2: Create New Database in FileMaker Cloud Identical in Structure to Existing On-Premise Database
Project staff will create a new (unpopulated) database on the FileMaker Cloud platform that duplicates the structure (schema) of the Agency's existing on-premise FileMaker database.
3.2.1.Create new database on FileMaker Cloud duplicating the existing on-premise database structure and function.
3.3. Phase 3: Transfer a Copy of the On-Premise FileMaker Database to FileMaker Cloud
Project staff will upload a copy of the Agency's on-premise FileMaker database to the new FileMaker Cloud database created in Phase 2. Using the existing on-premise database as a reference, project staff will then verify that the new cloud database is accurately populated and fully functional.
3.3.1.Verify readiness of on-premise FileMaker database copy for upload to FileMaker Cloud
3.3.2.Remediate any pre-upload issues (if necessary)
3.3.3.Upload database copy to FileMaker Cloud
3.3.4.Verify cloud database functionality and accuracy by...
3.3.4.1. Ensuring all records have successfully uploaded
3.3.4.2. Ensuring all record data fields function properly
3.3.4.3. Selecting at least 350 nonsequential records and comparing them to the same record in the on-premise database to ensure all data fields have properly populated
3.3.4.4. Certifying the above to the Agency
Note: Task 3.3.3 may be adjusted to uploading a sample of individual records should no backup copy of the Agency's entire database be successfully created during Phase 1. A modified version of Task 3.3.4 would then follow. The Agency and project staff will mutually agree upon a revised sample size for Task 3.3 and verification process for Task 3.4 if Phase 1 work cannot be completed.
Deliverables
Phase 1
(1) One (1) set of functional FileMaker Server administrator-level user access credentials.
(2) Two (2) backup copies of on-premise FileMaker database.
Phase 2
(3) New FileMaker Cloud database identical in structure and function to existing on-premise FileMaker database.
Phase 3
(4) Populated and functional FileMaker Cloud database.
(5) Certification that all database records have successfully transferred to cloud.
(6) Certification that all record data fields function properly.
(7) Report on test of 350 nonsequential records.
(8) Certification that cloud database is accurately populated and fully functional.
CANDIDATE SKILLS AND QUALIFICATIONS
Minimum 4 years of experience recovering administrative access to FileMaker Server, working with FileMaker Server and FileMaker Cloud, and transferring on-premise FileMaker databases to FileMaker Cloud.
OTHER SPECIAL REQUIREMENTS
The selected individual shall have experience in recovering administrative access to FileMaker Server v13 or a similar on-premise FileMaker Server version, experience in preparing and successfully transferring an on-premise FileMaker database to FileMaker Cloud, and experience in working with the Claris cloud platform, The selected staffing vendor must be headquartered within the United States
Location will be at - 1601 Congress Ave., Suite 3.500 Austin, Texas 78701 - Telework
Duration : Services are expected to start 10/20/2025 and are expected to complete by 12/15/2025. Total estimated hours per Candidate shall not exceed 120 hours. This service may be amended, renewed, and/or extended
I. DESCRIPTION OF SERVICES
1. Introduction
The Agency has an on-premise installation of Claris FileMaker Server v13 software. The Agency needs to recover administrative-level user access to this software and then port the database running on it to FileMaker Cloud. This project would occur in three successive phases.
In Phase 1 of the project, project staff will recover administrative-level user access to FileMaker Server v13. Project staff will then create new administrative-level user access credentials for the Agency. Finally, project staff will create two (2) backups of the database running on the FileMaker Server software.
In Phase 2 of the project, project staff will create a new database for the Agency on the FileMaker Cloud platform. This database will be identical to the structure (schema) of the Agency's existing on-premise FileMaker database.
In Phase 3 of the project, project staff will upload a copy of the Agency's on-premise FileMaker database to the new FileMaker Cloud database created in Phase 2. Project staff will then verify the success of the database transfer to the cloud via a series of verification checks.
2. Background
The Agency desires to modernize its database infrastructure by moving to FileMaker Cloud. To do this, the Agency needs project staff to access its instance of FileMaker Server v13 and backup the database running on it, create a new instance of its database on the FileMaker Cloud platform, and then transfer a copy of its existing on-premise FileMaker database to FileMaker Cloud.
The Agency's existing on-premise database has approximately 7,300 records. Each record has the same forty-five (45) fields:
- 25 Text fields
- 9 Number fields
- 4 Date fields
- 4 Calculation fields
- 3 Summary fields
The database does not appear to have any container fields. The Agency already has a subscription to FileMaker Cloud.
3. Scope of Work
3.1. Phase 1: Recover Admin-Level Access to FileMaker Server
Project staff will gain administrative-level user access to the Agency's on-premise instance FileMaker Server v13 and create a new set of administrative-level access credentials for the Agency. Project staff will then create two local backups of the Agency's FileMaker database.
3.1.1.Recover administrative-level user access to FileMaker Server v13.
3.1.2.Create one (1) set of administrative-level user access credentials to FileMaker Server.
3.1.3.Create two (2) backups of the database running on FileMaker Server.
3.2. Phase 2: Create New Database in FileMaker Cloud Identical in Structure to Existing On-Premise Database
Project staff will create a new (unpopulated) database on the FileMaker Cloud platform that duplicates the structure (schema) of the Agency's existing on-premise FileMaker database.
3.2.1.Create new database on FileMaker Cloud duplicating the existing on-premise database structure and function.
3.3. Phase 3: Transfer a Copy of the On-Premise FileMaker Database to FileMaker Cloud
Project staff will upload a copy of the Agency's on-premise FileMaker database to the new FileMaker Cloud database created in Phase 2. Using the existing on-premise database as a reference, project staff will then verify that the new cloud database is accurately populated and fully functional.
3.3.1.Verify readiness of on-premise FileMaker database copy for upload to FileMaker Cloud
3.3.2.Remediate any pre-upload issues (if necessary)
3.3.3.Upload database copy to FileMaker Cloud
3.3.4.Verify cloud database functionality and accuracy by...
3.3.4.1. Ensuring all records have successfully uploaded
3.3.4.2. Ensuring all record data fields function properly
3.3.4.3. Selecting at least 350 nonsequential records and comparing them to the same record in the on-premise database to ensure all data fields have properly populated
3.3.4.4. Certifying the above to the Agency
Note: Task 3.3.3 may be adjusted to uploading a sample of individual records should no backup copy of the Agency's entire database be successfully created during Phase 1. A modified version of Task 3.3.4 would then follow. The Agency and project staff will mutually agree upon a revised sample size for Task 3.3 and verification process for Task 3.4 if Phase 1 work cannot be completed.
Deliverables
Phase 1
(1) One (1) set of functional FileMaker Server administrator-level user access credentials.
(2) Two (2) backup copies of on-premise FileMaker database.
Phase 2
(3) New FileMaker Cloud database identical in structure and function to existing on-premise FileMaker database.
Phase 3
(4) Populated and functional FileMaker Cloud database.
(5) Certification that all database records have successfully transferred to cloud.
(6) Certification that all record data fields function properly.
(7) Report on test of 350 nonsequential records.
(8) Certification that cloud database is accurately populated and fully functional.
CANDIDATE SKILLS AND QUALIFICATIONS
Minimum 4 years of experience recovering administrative access to FileMaker Server, working with FileMaker Server and FileMaker Cloud, and transferring on-premise FileMaker databases to FileMaker Cloud.
OTHER SPECIAL REQUIREMENTS
The selected individual shall have experience in recovering administrative access to FileMaker Server v13 or a similar on-premise FileMaker Server version, experience in preparing and successfully transferring an on-premise FileMaker database to FileMaker Cloud, and experience in working with the Claris cloud platform, The selected staffing vendor must be headquartered within the United States