Overview
Skills
Job Details
Hi, this is Vijay Kumar from Cynosure Technologies LLC.
Reply requested for below Job from State of Texas
Role: FileMaker Database Administrator / Migration Specialist - Cloud
Location: Austin, TX Remote
Client: State of Texas
What the Client is Actually Looking For
The client s core need is modernizing and migrating their legacy FileMaker database from an on-premises FileMaker Server v13 to Claris FileMaker Cloud, while ensuring data integrity, schema duplication, and secure administrative access.
Key focus areas:
- FileMaker Server Access Recovery Someone who knows how to regain admin access on older versions (v13).
- Database Backup & Security Ability to create safe, redundant backups before migration.
- Schema Rebuild on FileMaker Cloud Duplicating the existing database structure (tables, fields, relationships, functions).
- Data Migration & Verification Transferring ~7,300 records accurately and testing functionality.
- Cloud Administration Post-migration verification, functionality checks, and certification.
The right consultant should be:
- A Claris FileMaker Developer/Consultant with hands-on experience in both FileMaker Server (older versions) and FileMaker Cloud.
- Strong background in FileMaker Pro / Claris database design, schema migration, and data integrity testing.
- Skilled in backup, recovery, and administration of FileMaker environments.
- Ideally Claris Certified Developer or consultant who has handled legacy to cloud migration projects.
Proper Job Title Suggestions
To reflect what the role really is, here are strong titles:
- FileMaker Cloud Migration Consultant
- Claris FileMaker Developer (Server to Cloud Migration)
- FileMaker Database Administrator / Migration Specialist
- FileMaker Server & Cloud Consultant
- Claris FileMaker Systems Migration Engineer
Best fit (clear + marketable):
FileMaker Cloud Migration Consultant
This title conveys both the technology (FileMaker) and the primary task (migration to cloud), which makes it easy for consultants to self-identify.
Introduction
The Agency has an on-premises 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-premises FileMaker database.
In Phase 3 of the project, project staff will upload a copy of the Agency s on-premises 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.
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-premises FileMaker database to FileMaker Cloud.
The Agency s existing on-premises 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.
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-premises 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-Premises 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-premises FileMaker database.
3.2.1.Create new database on FileMaker Cloud duplicating the existing on-premises database structure and function.
3.3. Phase 3: Transfer a Copy of the On-Premises FileMaker Database to FileMaker Cloud
Project staff will upload a copy of the Agency s on-premises FileMaker database to the new FileMaker Cloud database created in Phase 2. Using the existing on-premises 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-premises 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-premises 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-premises FileMaker database.
Phase 2
(3) New FileMaker Cloud database identical in structure and function to existing on-premises 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 Requirements: | ||
Years | Required/Preferred | Experience |
4 | Required | Experience recovering FileMaker Server access, experience working with FileMaker Server and FileMaker Cloud, and experience transferring on-prem FileMaker databases to FileMaker Cloud. |
Regards,
VIJAY KUMAR A
Sr. Technical Recruiter
Contact: +1 Ext 119
vkm
Cynosure Technologies, LLC
2401 Fountain View D, STE 502, Houston TX 77057